@apollo/rover
Supply chain provenance
Status for the latest visible version.
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): Apollo org migrated CI from CircleCI to GitHub Actions; SLSA provenance attestation confirms legitimate build pipeline. | ai | |
| install-scripts | install-script:postinstall | AI (install-scripts): Documented prebuilt-binary fetch for the Rover CLI; stable pattern across all versions of this package. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): child_process used to spawn the downloaded Rover binary; expected for this native-binary wrapper package. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 0.39.1 | 3 / 3 | |
| 0.38.1 | 3 / 3 | |
| 0.38.0 | 3 / 3 | |
| 0.37.0 | 5 / 4 | |
| 0.36.1 | 5 / 4 | |
| 0.34.1 | 5 / 4 | |
| 0.34.0 | 5 / 4 | |
| 0.32.0 | 5 / 4 | |
| 0.31.2 | 5 / 4 | |
| 0.31.1 | 5 / 4 | |
| 0.31.0 | 5 / 4 |
v0.39.1
2 findingsThis version was published by a different npm account than previous versions on 2026-05-20. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.38.1
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.38.0
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.37.0
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.36.1
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.1
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.34.0
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.32.0
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.2
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.1
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.31.0
2 findingsScript: node ./install.js
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.