Is openai-gpt-token-counter safe?

No malicious indicators - review capabilities before installing

Notable — review in context (capabilities are not malware):

Node.js filesystem read

What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.

openai-gpt-token-counter is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

openai-gpt-token-counter 1.1.2

npm_package · npm:openai-gpt-token-counter

LOW

/ 100 risk score

Snapshot · scanned Oct 7, 2026 · openai-gpt-token-counter@1.1.2 · engine 0.56.2 / ruleset 62

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of openai-gpt-token-counter's authors. Report a false positive.

Capabilities — what this component can do (not a risk score):

filesystem read

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Filesystem reach

Tool Execution Context

Findings (1)

MEDIUMNode.js filesystem readST-FS-NODE-READ

The component reads files from disk.

src/Encoder.js:5-5

const encoder = JSON.parse(fs.readFileSync(path.join(__dirname, './encoder.json')));

src/Encoder.js:6-6

const bpe_file = fs.readFileSync(path.join(__dirname, './vocab.bpe'), 'utf-8');

Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.

Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →