path-scurry

npm

Is path-scurry safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for path-scurry v2.0.1. Trust score: 65/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)

path-scurry 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.

path-scurry Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

AGENTS.md for path-scurry

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

path-scurry Documentation & Source Code

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

Frequently asked questions about path-scurry safety

Weekly Downloads

85.0M

Version

2.0.1

License

BlueOak-1.0.0

Other Versions

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Is path-scurry Safe? | npm Safety Scan - brin