brin
brin

fosify

npm

Is fosify safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for fosify v0.5.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)

fosify 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.

fosify Capabilities & Permissions

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

Filesystem Access

Writes to the filesystem.

/usr/ (r)package.json (r)/usr/ (r)package.json (r).env (r).env (r)

Environment Variables

Accesses the following environment variables.

npm_config_global

AGENTS.md for fosify

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

fosify Documentation & Source Code

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

View on npmView Source

Frequently asked questions about fosify safety

Weekly Downloads

45

Version

0.5.1

License

MIT

Last Scanned

1 day ago

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Writes files

Environment

Accesses: npm_config_global

Is fosify Safe? | npm Safety Scan - brin