@lokalise/fastify-api-contracts
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 7 of 7)
| Version | Deps | Published |
|---|---|---|
| 5.4.0 | 1 / 10 | |
| 5.3.1 | 0 / 10 | |
| 5.3.0 | 0 / 10 | |
| 5.2.0 | 0 / 10 | |
| 5.1.1 | 0 / 10 | |
| 5.1.0 | 0 / 10 | |
| 5.0.0 | 0 / 10 |
v5.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.3.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.2.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.