closure-compiler
Bindings to Google's Closure Compiler
17
Versions
MIT
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source, so a manually published version cannot be tied back to a reviewed commit.
Maintainers
mprobsttim-smart
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change from tim-smart to mprobst occurred in 2015; mprobst has 17 approved versions and a long track record. Legitimate historical transition, not a compromise. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): mprobst was added as maintainer in 2015 and has maintained the package for ~10 years with 17 approved versions. Stable, legitimate maintainer. | ai | |
| phantom-deps | phantom-dep:google-closure-compiler | AI (phantom-deps): google-closure-compiler is a runtime dependency used via shell/spawn rather than direct require(); expected pattern for a Java-based compiler wrapper. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): closure-compiler spawns a Java process to run the Closure Compiler JAR — child_process usage is the core, documented mechanism of this package and stable across all versions. | ai | |
| provenance | no-provenance | AI (provenance): Package predates Sigstore provenance by many years; absence is expected for this legacy package. | ai |