brin
brin

js-tokens

npm

Is js-tokens safe to use?

The latest brin safety scan flagged js-tokens v10.0.0 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 65/100. Review the findings below before use. This is an automated assessment and may contain errors.

Install (safety-checked)

js-tokens Has Warnings

Warnings detected due to potential concerns

warning
CVEs

0

Threats

0

Install Scripts

0

Risk Indicators

  • •Can spawn child processes

brin Recommendations

  • →This package has warnings detected. Evaluate the specific concerns before proceeding.

Install with brin add js-tokens to automatically apply these checks before installation.

This is an automated, point-in-time assessment and may contain errors. Findings are risk indicators, not confirmed threats. Security posture may change over time. Maintainers can dispute findings via the brin review process.

js-tokens Capabilities & Permissions

What js-tokens can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Process Spawning

This package can spawn child processes.

AGENTS.md for js-tokens

Good instructions lead to good results. brin adds js-tokens documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.

brin init

Vercel's research: 100% accuracy with AGENTS.md vs 53% without →

js-tokens Documentation & Source Code

For the full js-tokens README, API documentation, and source code, visit the official package registry.

View on npmView SourceHomepage

Frequently asked questions about js-tokens safety

Weekly Downloads

102.0M

Version

10.0.0

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes

Is js-tokens Safe? | npm Safety Scan - brin