JavaScript parser, mangler/compressor and beautifier toolkit
58%
Total Score
50
100
86
50
50
No build attestation or staged publishing is reported, reducing publication transparency, although this is a secondary concern for an established package with a matching repository.
The package has 288 releases and a long history, but its latest registry release was about two years ago and it had no releases in the last 12 months. This is a meaningful maintenance concern despite the historically strong cadence.
The repository recorded no commits and no active maintainers in the last three months, reinforcing the release-history warning and raising abandonment risk.
There were no new or closed issues or pull requests in the last month, so the repository shows little recent maintenance activity.
The repository reports no build tooling and no security scanning tooling, leaving less automated assurance around future changes.
| Title | Versions | Severity |
|---|---|---|
CVE-2015-8857 uglify-js is vulnerable to Always-Incorrect Control Flow Implementation in versions 0.0.0 - 2.4.24. | 0.0.0 - 2.4.24 | Critical |
CVE-2015-8858 uglify-js is vulnerable to Inefficient Regular Expression Complexity in versions 0.0.0 - 2.6.0. | 0.0.0 - 2.6.0 | High |
No direct dependencies.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.