@contentstack/cli-variants
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 |
|---|---|---|---|---|
| semgrep | semgrep:dynamic-require | AI (semgrep): Loads user-configured mock data path for testing; not an arbitrary code execution vector in this context. | ai | |
| phantom-deps | phantom-dep:@oclif/core | AI (phantom-deps): @oclif/core is referenced in oclif config blocks, not directly imported in source — stable false positive for oclif plugins. | ai | |
| phantom-deps | phantom-dep:@oclif/plugin-help | AI (phantom-deps): @oclif/plugin-help is a standard oclif config dependency, not directly imported — stable false positive for oclif plugins. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.5.1 | 5 / 7 | |
| 1.5.0 | 5 / 7 | |
| 1.4.3 | 5 / 7 | |
| 1.4.2 | 6 / 8 | |
| 1.4.1 | 6 / 8 | |
| 1.4.0 | 6 / 8 | |
| 1.3.8 | 6 / 8 | |
| 1.3.7 | 6 / 8 | |
| 1.3.6 | 6 / 8 | |
| 1.3.5 | 6 / 8 | |
| 1.3.4 | 6 / 8 | |
| 1.3.3 | 6 / 8 | |
| 1.3.2 | 6 / 8 | |
| 1.3.0 | 6 / 8 | |
| 1.2.2 | 4 / 7 | |
| 1.2.1 | 4 / 7 |
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.6
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.2
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.