log4js
npmIs log4js safe to use?
The latest brin safety scan flagged log4js v6.9.1 with risk indicators that warrant review. No known CVE vulnerabilities. Trust score: 75/100. Review the findings below before use. This is an automated assessment and may contain errors.
Install (safety-checked)
log4js Has Warnings
Warnings detected due to potential concerns
0
0
0
Risk Indicators
- •Can spawn child processes
brin Recommendations
- →This package has warnings detected. Evaluate the specific concerns before proceeding.
Install with brin add log4js to automatically apply these checks before installation.
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.
log4js Capabilities & Permissions
What log4js can access when installed. Review these capabilities before using with AI agents like Cursor, Claude Code, or Codex.
Network Access
This package makes network requests.
Filesystem Access
Reads and writes to the filesystem.
Process Spawning
This package can spawn child processes.
Environment Variables
Accesses the following environment variables.
AGENTS.md for log4js
Good instructions lead to good results. brin adds log4js documentation to your AGENTS.md so your agent knows how to use it properly—improving both safety and performance.
brin initVercel's research: 100% accuracy with AGENTS.md vs 53% without →
log4js Documentation & Source Code
For the full log4js README, API documentation, and source code, visit the official package registry.
Frequently asked questions about log4js safety
Install (safety-checked)
Weekly Downloads
Version
6.9.1License
Apache-2.0Last Scanned
Trust Score
Capabilities
Connects to: example.com, github.com, jroller.com...
Reads & Writes files
Spawns child processes
Accesses: LOG4JS_CONFIG