package-hash

npm

Is package-hash safe to use?

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

Install (safety-checked)

package-hash 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 package-hash 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.

package-hash Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

.env (r)package.json (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for package-hash

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

package-hash Documentation & Source Code

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

Frequently asked questions about package-hash safety

Weekly Downloads

5.9M

Version

4.0.0

License

ISC

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is package-hash Safe? | npm Safety Scan - brin