@tryghost/kg-card-factory
`npm install @tryghost/kg-card-factory --save`
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 13 of 13)
| Version | Deps | Published |
|---|---|---|
| 5.2.2 | 0 / 13 | |
| 5.2.1 | 0 / 13 | |
| 5.2.0 | 0 / 13 | |
| 5.1.14 | 0 / 13 | |
| 5.1.13 | 0 / 13 | |
| 5.1.12 | 0 / 5 | |
| 5.1.11 | 0 / 5 | |
| 5.1.10 | 0 / 5 | |
| 5.1.9 | 0 / 5 | |
| 5.1.5 | 0 / 5 | |
| 5.1.3 | 0 / 5 | |
| 5.1.2 | 0 / 5 | |
| 5.1.1 | 0 / 5 |
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.14
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.13
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.12
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.11
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.10
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.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.1.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
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.