uglify-js2

npm

Is uglify-js2 safe to use?

Based on the latest brin safety scan, no vulnerabilities or threats were detected for uglify-js2 v2.1.11. Trust score: 55/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)

uglify-js2 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.

uglify-js2 Capabilities & Permissions

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

Filesystem Access

Reads from the filesystem.

/usr/ (r)

Process Spawning

This package can spawn child processes.

AGENTS.md for uglify-js2

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

uglify-js2 Documentation & Source Code

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

Frequently asked questions about uglify-js2 safety

Weekly Downloads

86

Version

2.1.11

Last Scanned

5 hours ago

Trust Score

55/100·Legitimacy signals, not safety

Capabilities

Filesystem

Reads files

Process

Spawns child processes

Is uglify-js2 Safe? | npm Safety Scan - brin