@contentstack/cli-auth
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.4 | 4 / 17 | |
| 1.8.3 | 4 / 17 | |
| 1.8.2 | 4 / 17 | |
| 1.8.1 | 5 / 19 | |
| 1.8.0 | 5 / 19 | |
| 1.7.3 | 5 / 19 | |
| 1.7.2 | 5 / 19 | |
| 1.7.1 | 5 / 19 | |
| 1.7.0 | 5 / 19 | |
| 1.6.3 | 5 / 19 | |
| 1.6.2 | 5 / 19 | |
| 1.6.1 | 5 / 19 | |
| 1.6.0 | 5 / 19 | |
| 1.5.1 | 4 / 19 | |
| 1.5.0 | 4 / 19 | |
| 1.4.1 | 2 / 19 | |
| 1.4.0 | 2 / 19 | |
| 1.3.25 | 2 / 19 | |
| 1.3.24 | 2 / 19 | |
| 1.3.23 | 2 / 19 |
v1.8.4
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.25
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.3.24
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.3.23
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.