@contentstack/cli-cm-bootstrap
Bootstrap contentstack apps
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 |
|---|---|---|---|---|
| dependencies | unvetted-dep:@contentstack/cli-config | AI (dependencies): First-party Contentstack sibling package; stable pattern across all versions of this CLI plugin. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): Bootstrap/scaffolding tool legitimately uses child_process to run CLI commands; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/core | AI (phantom-deps): oclif framework dep referenced in config/manifest; not a direct import but legitimately declared. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): oclif plugin-help is a framework-level dep declared for oclif config, not directly imported in source. | ai |
Versions (showing 17 of 17)
| Version | Deps | Published |
|---|---|---|
| 1.19.4 | 8 / 12 | |
| 1.19.3 | 8 / 12 | |
| 1.19.2 | 8 / 12 | |
| 1.19.1 | 9 / 15 | |
| 1.19.0 | 9 / 15 | |
| 1.18.4 | 9 / 15 | |
| 1.18.3 | 9 / 15 | |
| 1.18.2 | 8 / 15 | |
| 1.18.1 | 8 / 15 | |
| 1.18.0 | 8 / 15 | |
| 1.17.2 | 8 / 15 | |
| 1.17.1 | 8 / 15 | |
| 1.17.0 | 8 / 15 | |
| 1.16.1 | 8 / 15 | |
| 1.16.0 | 8 / 15 | |
| 1.15.0 | 8 / 15 | |
| 1.14.1 | 6 / 15 |
v1.19.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.19.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.18.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.18.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.17.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.16.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.15.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.