brin
brin

scss-tokenizer

npm

Is scss-tokenizer safe to use?

The latest brin safety scan flagged scss-tokenizer v0.4.3 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)

scss-tokenizer 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 scss-tokenizer 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.

scss-tokenizer Capabilities & Permissions

What scss-tokenizer 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 scss-tokenizer

Good instructions lead to good results. brin adds scss-tokenizer 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 →

scss-tokenizer Documentation & Source Code

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

View on npmView Source

Frequently asked questions about scss-tokenizer safety

Weekly Downloads

919.3K

Version

0.4.3

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Process

Spawns child processes