@astrojs/ts-plugin
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 1.10.10 | 7 / 10 | |
| 1.10.9 | 7 / 10 | |
| 1.10.8 | 7 / 10 | |
| 1.10.7 | 7 / 8 | |
| 1.10.6 | 7 / 8 | |
| 1.10.5 | 7 / 10 | |
| 1.10.4 | 7 / 10 | |
| 1.10.3 | 7 / 10 | |
| 1.10.2 | 7 / 9 | |
| 1.10.1 | 7 / 9 | |
| 1.10.0 | 7 / 9 | |
| 1.9.3 | 6 / 7 | |
| 1.9.2 | 6 / 7 | |
| 1.9.1 | 6 / 7 | |
| 1.9.0 | 6 / 7 | |
| 1.8.0 | 6 / 7 |
v1.10.10
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.10.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.10.1
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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.9.1
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. Only ~12% of npm packages have provenance, so this is common but not ideal.