@contentstack/cli-audit
Contentstack audit 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, 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:@oclif/plugin-help | AI (phantom-deps): @oclif/plugin-help is referenced in oclif config as a plugin, not a direct import — stable false positive for this package. | ai |
Versions (showing 35 of 35)
| Version | Deps | Published |
|---|---|---|
| 1.19.5 | 8 / 16 | |
| 1.19.4 | 8 / 16 | |
| 1.19.3 | 8 / 16 | |
| 1.19.2 | 10 / 17 | |
| 1.19.1 | 11 / 17 | |
| 1.19.0 | 11 / 17 | |
| 1.18.0 | 11 / 17 | |
| 1.17.1 | 11 / 17 | |
| 1.17.0 | 11 / 17 | |
| 1.16.2 | 11 / 17 | |
| 1.16.1 | 11 / 17 | |
| 1.16.0 | 11 / 17 | |
| 1.15.0 | 11 / 17 | |
| 1.14.2 | 11 / 17 | |
| 1.14.1 | 11 / 17 | |
| 1.14.0 | 11 / 17 | |
| 1.13.0 | 10 / 17 | |
| 1.12.1 | 10 / 17 | |
| 1.12.0 | 10 / 17 | |
| 1.11.0 | 10 / 17 | |
| 1.10.0 | 10 / 17 | |
| 1.9.0 | 10 / 17 | |
| 1.8.0 | 10 / 17 | |
| 1.7.5 | 10 / 17 | |
| 1.7.4 | 10 / 20 | |
| 1.7.3 | 10 / 20 | |
| 1.7.2 | 10 / 20 | |
| 1.7.1 | 10 / 20 | |
| 1.7.0 | 10 / 20 | |
| 1.6.5 | 10 / 20 | |
| 1.6.4 | 10 / 20 | |
| 1.6.3 | 10 / 20 | |
| 1.6.2 | 10 / 20 | |
| 1.6.1 | 10 / 20 | |
| 1.6.0 | 10 / 20 |
v1.19.5
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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.12.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.0
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.7.2
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.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.6.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.