@supabase/phoenix
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 6 of 6)
| Version | Deps | Published |
|---|---|---|
| 0.4.2 | 0 / 13 | |
| 0.4.1 | 0 / 13 | |
| 0.4.0 | 0 / 13 | |
| 0.3.1 | 0 / 13 | |
| 0.2.0 | 0 / 13 | |
| 0.1.0 | 0 / 13 |
v0.4.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.1.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.