google-closure-compiler-js
Check, compile, optimize and compress Javascript with Closure-Compiler using Java
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 |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Both lharker and blickly are Google engineers on the Closure Compiler project; maintainer transitions within the same org are expected and not a risk signal for this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process is used in build_compiler.js, a dev/build script invoked only during testing, not at install or runtime. Expected for a compiler toolchain package. | ai |
Versions (showing 63 of 63)
v20200719.0.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v20180610.0.0
2 findingsThis version was published by a different npm account than previous versions on 2018-06-13. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.