@vlandoss/loggy
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 10 of 10)
| Version | Deps | Published |
|---|---|---|
| 0.2.1 | 2 / 2 | |
| 0.2.0 | 2 / 2 | |
| 0.1.1 | 2 / 2 | |
| 0.1.0 | 2 / 2 | |
| 0.0.7 | 2 / 1 | |
| 0.0.6 | 2 / 1 | |
| 0.0.5 | 2 / 1 | |
| 0.0.4 | 2 / 1 | |
| 0.0.3 | 2 / 1 | |
| 0.0.2 | 2 / 1 |
v0.2.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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.1.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.0.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.