debuglog

npm

Is debuglog safe to use?

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

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

debuglog Capabilities & Permissions

What debuglog 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_DEBUG

AGENTS.md for debuglog

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

debuglog Documentation & Source Code

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

Frequently asked questions about debuglog safety

Weekly Downloads

3.1M

Version

1.0.1

License

MIT

Last Scanned

Jan 31, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: NODE_DEBUG

Is debuglog Safe? | npm Safety Scan - brin