log-node

npm

Is log-node safe to use?

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

log-node 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.

log-node Capabilities & Permissions

What log-node 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_COLORSDEBUG_DEPTHLOG_INSPECT_DEPTH

AGENTS.md for log-node

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

log-node Documentation & Source Code

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

Frequently asked questions about log-node safety

Weekly Downloads

835.7K

Version

8.0.3

License

ISC

Last Scanned

Feb 1, 2026

Trust Score

65/100·Legitimacy signals, not safety

Capabilities

Environment

Accesses: DEBUG_COLORS, DEBUG_DEPTH, LOG_INSPECT_DEPTH

Is log-node Safe? | npm Safety Scan - brin