config

npm

Is config safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for config v4.2.0. Trust score: 75/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)

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

config Capabilities & Permissions

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

Environment Variables

Accesses the following environment variables.

NODE_CONFIGNODE_CONFIG_STRICT_MODE

AGENTS.md for config

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

config Documentation & Source Code

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

Frequently asked questions about config safety

Weekly Downloads

1.4M

Version

4.2.0

License

MIT

Other Versions

Last Scanned

Feb 1, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: NODE_CONFIG, NODE_CONFIG_STRICT_MODE

Is config Safe? | npm Safety Scan - brin