ts-ics
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
Versions (showing 25 of 25)
| Version | Deps | Published |
|---|---|---|
| 2.4.6 | 1 / 12 | |
| 2.4.5 | 1 / 12 | |
| 2.4.4 | 1 / 12 | |
| 2.4.3 | 1 / 12 | |
| 2.4.2 | 1 / 12 | |
| 2.4.1 | 1 / 12 | |
| 2.4.0 | 1 / 12 | |
| 2.3.1 | 1 / 12 | |
| 2.3.0 | 1 / 12 | |
| 2.2.0 | 1 / 12 | |
| 2.1.8 | 1 / 12 | |
| 2.1.7 | 1 / 12 | |
| 2.1.6 | 1 / 12 | |
| 2.1.5 | 1 / 12 | |
| 2.1.4 | 1 / 12 | |
| 2.1.3 | 1 / 12 | |
| 2.1.2 | 1 / 12 | |
| 2.1.1 | 1 / 12 | |
| 2.1.0 | 1 / 12 | |
| 2.0.5 | 1 / 12 | |
| 2.0.4 | 1 / 12 | |
| 2.0.3 | 1 / 12 | |
| 2.0.2 | 1 / 12 | |
| 2.0.1 | 1 / 12 | |
| 2.0.0 | 1 / 12 |
v2.1.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v2.0.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v2.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.