node-minify
Javascript / CSS minifier based on Babel-minify / Butternut / YUI Compressor / Google Closure Compiler / UglifyJS2 / Sqwish / Clean-css / CSSO
Supply chain provenance
Status for the latest visible version.
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| dependencies | unvetted-dep:html-minifier | AI (dependencies): html-minifier is a well-known, widely-used HTML minification library; unvetted flag is a false positive for this established dependency. | ai | |
| semgrep | semgrep:child-process-spawn | AI (semgrep): node-minify spawns Java to run YUI/GCC minifiers — this is core documented functionality, not malicious code execution. | ai | |
| semgrep | semgrep:shady-links-raw-ip | AI (semgrep): Flagged line is a console.log of localhost (127.0.0.1) in an example server script — no real HTTP request, no exfiltration risk. Stable false positive for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process import is required for spawning Java-based minifier backends; stable legitimate use for this package. | ai |
Versions (showing 51 of 79)
| Version | Deps | Published |
|---|---|---|
| 3.6.0 | 21 / 9 | |
| 3.5.0 | 21 / 9 | |
| 3.3.0 | 20 / 9 | |
| 3.2.1 | 21 / 9 | |
| 3.2.0 | 21 / 9 | |
| 3.1.2 | 20 / 9 | |
| 3.1.1 | 20 / 9 | |
| 3.1.0 | 20 / 9 | |
| 3.0.1 | 19 / 9 | |
| 3.0.0 | 19 / 9 | |
| 2.4.2 | 13 / 9 | |
| 2.4.1 | 13 / 9 | |
| 2.4.0 | 13 / 8 | |
| 2.3.1 | 13 / 8 | |
| 2.3.0 | 13 / 3 | |
| 2.2.0 | 13 / 3 | |
| 2.1.1 | 13 / 3 | |
| 2.1.0 | 13 / 3 | |
| 2.0.5 | 13 / 9 | |
| 2.0.4 | 13 / 9 | |
| 2.0.3 | 13 / 9 | |
| 2.0.2 | 13 / 9 | |
| 2.0.0 | 13 / 8 | |
| 1.3.9 | 7 / 14 | |
| 1.3.8 | 7 / 14 | |
| 1.3.7 | 7 / 14 | |
| 1.3.6 | 7 / 14 | |
| 1.3.5 | 7 / 14 | |
| 1.3.4 | 7 / 14 | |
| 1.3.3 | 7 / 14 | |
| 1.3.2 | 7 / 10 | |
| 1.3.1 | 7 / 10 | |
| 1.3.0 | 7 / 10 | |
| 1.2.1 | 7 / 10 | |
| 1.2.0 | 7 / 10 | |
| 1.1.0 | 7 / 10 | |
| 1.0.2 | 7 / 10 | |
| 1.0.1 | 7 / 10 | |
| 1.0.0 | 7 / 10 | |
| 0.13.1 | 7 / 7 | |
| 0.12.1 | 7 / 7 | |
| 0.11.1 | 6 / 7 | |
| 0.10.5 | 6 / 7 | |
| 0.10.4 | 6 / 7 | |
| 0.10.3 | 6 / 7 | |
| 0.10.2 | 5 / 7 | |
| 0.10.1 | 5 / 7 | |
| 0.9.4 | 3 / 7 | |
| 0.9.3 | 3 / 7 | |
| 0.9.2 | 3 / 0 | |
| 0.9.1 | 3 / 0 |
v3.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v3.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.