debug

npm

Is debug safe to use?

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

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

debug Capabilities & Permissions

What debug 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.

DEBUG

AGENTS.md for debug

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

debug Documentation & Source Code

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

Frequently asked questions about debug safety

Weekly Downloads

449.3M

Version

4.4.3

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

75/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: DEBUG

Is debug Safe? | npm Safety Scan - brin