@contentstack/cli-cm-branches
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 20 of 20)
| Version | Deps | Published |
|---|---|---|
| 1.8.3 | 6 / 11 | |
| 1.8.2 | 6 / 11 | |
| 1.8.1 | 6 / 11 | |
| 1.8.0 | 7 / 14 | |
| 1.7.1 | 7 / 14 | |
| 1.7.0 | 7 / 14 | |
| 1.6.3 | 7 / 14 | |
| 1.6.2 | 7 / 14 | |
| 1.6.1 | 7 / 14 | |
| 1.6.0 | 7 / 14 | |
| 1.5.2 | 7 / 14 | |
| 1.5.1 | 7 / 14 | |
| 1.5.0 | 7 / 14 | |
| 1.4.3 | 6 / 14 | |
| 1.4.2 | 6 / 14 | |
| 1.4.1 | 6 / 14 | |
| 1.4.0 | 6 / 14 | |
| 1.3.1 | 6 / 14 | |
| 1.3.0 | 6 / 14 | |
| 1.2.1 | 6 / 14 |
v1.8.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. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.1
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.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.