@enonic-types/lib-event
Type definitions for lib-event.
Supply chain provenance
Status for the latest visible version.
Maintainers
Keywords
Versions (showing 8 of 8)
| Version | Deps | Published |
|---|---|---|
| 7.16.4 | 0 / 0 | |
| 7.16.3 | 0 / 0 | |
| 7.16.2 | 0 / 0 | |
| 7.16.1 | 0 / 0 | |
| 7.16.0 | 0 / 0 | |
| 7.15.4 | 0 / 0 | |
| 7.15.3 | 0 / 0 | |
| 7.15.2 | 0 / 0 |
v7.16.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v7.16.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.16.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v7.15.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v7.15.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.