@contentstack/cli-launch
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 |
|---|---|---|---|---|
| phantom-deps | phantom-dep:graphql | AI (phantom-deps): Referenced in oclif config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): Declared in oclif.plugins config; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/express | AI (phantom-deps): TypeScript framework types; stable convention for this package. | ai | |
| phantom-deps | phantom-dep:@rollup/plugin-typescript | AI (phantom-deps): Build tool plugin; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@types/express-serve-static-core | AI (phantom-deps): TypeScript framework types; stable convention for this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.10.0 | 23 / 24 | |
| 1.9.9 | 23 / 24 | |
| 1.9.8 | 23 / 24 | |
| 1.9.7 | 23 / 24 | |
| 1.9.6 | 23 / 24 | |
| 1.9.5 | 24 / 24 | |
| 1.9.4 | 24 / 24 | |
| 1.9.3 | 24 / 24 | |
| 1.9.2 | 24 / 24 |
v1.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.7
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.4
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.9.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.