@contentstack/cli-cm-clone
Contentstack stack clone plugin
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:@contentstack/cli-utilities | AI (phantom-deps): Same-org scoped package used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:ora | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:chalk | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:merge | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:prompt | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:rimraf | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:inquirer | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@colors/colors | AI (phantom-deps): Indirect dependency used through config/transitive imports; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contentstack/cli-command | AI (phantom-deps): Same-org scoped package used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contentstack/cli-cm-export | AI (phantom-deps): Same-org scoped package used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@contentstack/cli-cm-import | AI (phantom-deps): Same-org scoped package used indirectly; stable pattern for this package. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): @oclif/plugin-help is declared as a runtime dep and referenced in oclif config; not a real phantom dep for this package. | ai |
Versions (showing 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.21.6 | 13 / 15 | |
| 1.21.5 | 13 / 15 | |
| 1.21.4 | 13 / 15 | |
| 1.21.3 | 13 / 15 | |
| 1.21.2 | 14 / 15 | |
| 1.21.1 | 14 / 15 | |
| 1.21.0 | 14 / 15 | |
| 1.20.1 | 14 / 15 | |
| 1.20.0 | 14 / 15 | |
| 1.19.0 | 14 / 8 | |
| 1.18.1 | 14 / 8 | |
| 1.18.0 | 14 / 8 | |
| 1.17.0 | 15 / 8 | |
| 1.16.1 | 15 / 8 | |
| 1.16.0 | 15 / 8 | |
| 1.15.1 | 15 / 8 | |
| 1.15.0 | 15 / 8 | |
| 1.14.3 | 15 / 8 | |
| 1.14.2 | 13 / 8 | |
| 1.14.1 | 13 / 8 |
v1.21.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.21.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.21.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.20.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.20.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.19.0
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.1
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. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.14.2
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.