@coveo/raptor-cli
A smaller and smarter dinosaur
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
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugin loaded by convention via oclif.manifest config, not direct import; stable false positive for oclif CLIs. | ai | |
| phantom-deps | phantom-dep:indent-string | AI (phantom-deps): Utility dep referenced in config/build context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:sleep-promise | AI (phantom-deps): Utility dep referenced in config/build context; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@types/chrome-remote-interface | AI (phantom-deps): Type-only package loaded by framework convention; stable false positive. | ai |
Versions (showing 11 of 11)
| Version | Deps | Published |
|---|---|---|
| 1.8.2 | 29 / 4 | |
| 1.8.1 | 29 / 4 | |
| 1.7.1 | 27 / 4 | |
| 1.7.0 | 27 / 4 | |
| 1.6.0 | 25 / 4 | |
| 1.5.1 | 25 / 4 | |
| 1.5.0 | 25 / 4 | |
| 1.4.0 | 20 / 4 | |
| 1.3.0 | 20 / 4 | |
| 1.2.0 | 20 / 4 | |
| 1.1.1 | 19 / 4 |
v1.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.7.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.