npm-conf

npm

Is npm-conf safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for npm-conf v1.1.3. 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)

npm-conf 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.

npm-conf Capabilities & Permissions

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

Filesystem Access

Reads and writes to the filesystem.

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

Environment Variables

Accesses the following environment variables.

APPDATACICOMSPECDESTDIREDITORHOMENODE_ENVPREFIXSHELLSUDO_GID+3 more

AGENTS.md for npm-conf

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

npm-conf Documentation & Source Code

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

Frequently asked questions about npm-conf safety

Weekly Downloads

1.3M

Version

1.1.3

License

MIT

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads & Writes files

Environment

Accesses: APPDATA, CI, COMSPEC...

Is npm-conf Safe? | npm Safety Scan - brin