@contentstack/cli-cm-export-to-csv
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
Versions (showing 21 of 21)
| Version | Deps | Published |
|---|---|---|
| 1.12.6 | 6 / 15 | |
| 1.12.5 | 6 / 15 | |
| 1.12.4 | 6 / 15 | |
| 1.12.3 | 6 / 15 | |
| 1.12.2 | 6 / 15 | |
| 1.12.1 | 8 / 17 | |
| 1.12.0 | 8 / 17 | |
| 1.11.0 | 8 / 17 | |
| 1.10.2 | 8 / 10 | |
| 1.10.1 | 8 / 10 | |
| 1.10.0 | 8 / 10 | |
| 1.9.2 | 8 / 10 | |
| 1.9.1 | 8 / 10 | |
| 1.9.0 | 8 / 10 | |
| 1.8.2 | 6 / 10 | |
| 1.8.1 | 6 / 10 | |
| 1.8.0 | 6 / 10 | |
| 1.7.4 | 6 / 10 | |
| 1.7.3 | 7 / 12 | |
| 1.7.2 | 7 / 12 | |
| 1.7.1 | 7 / 12 |
v1.12.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.12.5
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.