@tryghost/kg-default-atoms
`npm install @tryghost/kg-default-atoms --save`
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 12 of 12)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 0 / 13 | |
| 5.2.1 | 0 / 13 | |
| 5.2.0 | 0 / 13 | |
| 5.1.9 | 0 / 13 | |
| 5.1.8 | 0 / 13 | |
| 5.1.7 | 0 / 2 | |
| 5.1.6 | 0 / 2 | |
| 5.1.5 | 0 / 2 | |
| 5.1.4 | 0 / 2 | |
| 5.1.3 | 0 / 2 | |
| 5.1.2 | 0 / 2 | |
| 5.1.1 | 0 / 2 |
v5.2.2
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.9
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.8
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.7
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.6
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.5
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.4
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.