@contentstack/cli-cm-export
Contentstack CLI plugin to export content from stack
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Internal module-loader pattern resolving known sibling module files; stable across versions of this package. | ai | |
| phantom-deps | phantom-dep:@oclif/core | AI (phantom-deps): @oclif/core is declared in dependencies and used via oclif framework config; phantom-dep is a false positive here. | ai |
Versions (showing 40 of 40)
| Version | Deps | Published |
|---|---|---|
| 1.25.3 | 14 / 22 | |
| 1.25.2 | 14 / 22 | |
| 1.25.1 | 14 / 22 | |
| 1.25.0 | 14 / 22 | |
| 1.24.3 | 14 / 22 | |
| 1.24.2 | 14 / 23 | |
| 1.24.1 | 14 / 23 | |
| 1.24.0 | 14 / 23 | |
| 1.23.2 | 14 / 23 | |
| 1.23.1 | 14 / 23 | |
| 1.23.0 | 14 / 23 | |
| 1.22.2 | 14 / 23 | |
| 1.22.1 | 14 / 23 | |
| 1.22.0 | 14 / 23 | |
| 1.21.0 | 14 / 23 | |
| 1.20.2 | 14 / 17 | |
| 1.20.1 | 14 / 17 | |
| 1.20.0 | 14 / 17 | |
| 1.19.0 | 14 / 17 | |
| 1.18.1 | 14 / 17 | |
| 1.18.0 | 14 / 17 | |
| 1.17.0 | 14 / 17 | |
| 1.16.3 | 14 / 17 | |
| 1.16.2 | 14 / 17 | |
| 1.16.1 | 14 / 17 | |
| 1.16.0 | 14 / 17 | |
| 1.15.2 | 14 / 17 | |
| 1.15.0 | 14 / 17 | |
| 1.14.2 | 14 / 17 | |
| 1.14.1 | 18 / 21 | |
| 1.14.0 | 18 / 21 | |
| 1.13.0 | 18 / 21 | |
| 1.12.1 | 18 / 21 | |
| 1.12.0 | 18 / 21 | |
| 1.11.7 | 17 / 21 | |
| 1.11.6 | 17 / 21 | |
| 1.11.5 | 17 / 21 | |
| 1.11.4 | 17 / 21 | |
| 1.11.3 | 17 / 21 | |
| 1.11.2 | 17 / 21 |
v1.25.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.25.2
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.2
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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.14.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.11.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.