@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, so a manually published version cannot be tied back to a reviewed commit.
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 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 1.11.1 | 23 / 24 | |
| 1.11.0 | 23 / 24 | |
| 1.10.1 | 23 / 24 | |
| 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 | |
| 1.9.1 | 24 / 24 | |
| 1.9.0 | 24 / 24 | |
| 1.8.0 | 24 / 23 | |
| 1.7.1 | 24 / 20 | |
| 1.7.0 | 24 / 20 | |
| 1.6.0 | 24 / 20 | |
| 1.5.2 | 24 / 20 | |
| 1.5.1 | 24 / 20 | |
| 1.5.0 | 20 / 21 | |
| 1.4.1 | 20 / 21 | |
| 1.3.1 | 20 / 16 | |
| 1.3.0 | 20 / 16 | |
| 1.2.3 | 20 / 16 | |
| 1.2.2 | 20 / 16 | |
| 1.2.1 | 20 / 16 | |
| 1.2.0 | 20 / 16 | |
| 1.1.0 | 20 / 16 | |
| 1.0.19 | 20 / 16 | |
| 1.0.18 | 20 / 16 |
v1.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.2
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.2.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.0.18
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.