@cmsfe/tools

npm

Is @cmsfe/tools safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for @cmsfe/tools v2.0.34. Trust score: 55/100. No known CVE vulnerabilities, no detected threat patterns, and no suspicious capabilities identified. This is an automated, point-in-time assessment.

Install (safety-checked)

@cmsfe/tools Passed Security Checks

No security concerns detected

clean
CVEs

0

Threats

0

Install Scripts

0

No Concerns Detected

No security concerns detected in the latest brin assessment. This is an automated, point-in-time evaluation — security posture may change.

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.

@cmsfe/tools Capabilities & Permissions

What @cmsfe/tools can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.

Network Access

This package makes network requests.

feross.orgfeross.org>github.com
Protocols: https

Process Spawning

This package can spawn child processes.

AGENTS.md for @cmsfe/tools

Good instructions lead to good results. brin adds @cmsfe/tools 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 →

@cmsfe/tools Documentation & Source Code

For the full @cmsfe/tools README, API documentation, and source code, visit the official package registry.

Frequently asked questions about @cmsfe/tools safety

Weekly Downloads

66

Version

2.0.34

License

MIT

Last Scanned

3 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Network

Connects to: feross.org, feross.org>, github.com

Process

Spawns child processes

Is @cmsfe/tools Safe? | npm Safety Scan - brin