@tryghost/kg-card-factory
`npm install @tryghost/kg-card-factory --save`
Supply chain provenance
Status for the latest visible version.
Maintainers
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): CI/CD migration with SLSA attestation, improved provenance, consistent with monorepo automation. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Expected fallout of switching to automated org-level publishing, not a takeover signal. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Monorepo subpackage; no description is cosmetic, not a malware indicator. | ai |
Versions (showing 26 of 26)
| Version | Deps | Published |
|---|---|---|
| 5.2.4 | 0 / 7 | |
| 5.2.3 | 0 / 13 | |
| 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.8 | 0 / 5 | |
| 5.1.7 | 0 / 5 | |
| 5.1.6 | 0 / 5 | |
| 5.1.5 | 0 / 5 | |
| 5.1.3 | 0 / 5 | |
| 5.1.2 | 0 / 5 | |
| 5.1.1 | 0 / 5 | |
| 5.1.0 | 0 / 5 | |
| 5.0.6 | 0 / 5 | |
| 5.0.5 | 0 / 5 | |
| 5.0.4 | 0 / 5 | |
| 5.0.3 | 0 / 5 | |
| 5.0.2 | 0 / 5 | |
| 5.0.1 | 0 / 5 | |
| 5.0.0 | 0 / 5 |
v5.2.4
2 findingsThis version has no gitHead field linking it to a source commit, but previous versions did. This suggests the publish environment changed. Published by: GitHub Actions.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.8
2 findingsThis version was published by a different npm account than previous versions on 2026-02-05. This could indicate a legitimate maintainer transition or an account compromise.
Published via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v5.1.7
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (tmciesco) than the most recent previously approved version (chrisraible) on 2026-01-22, but tmciesco is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.1.6
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (chrisraible) than the most recent previously approved version (vershwal) on 2026-01-15, but chrisraible is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
This version was published by a different npm account (daniellockyer) than the most recent previously approved version (kevinansfield) on 2025-02-17, but daniellockyer is listed as a maintainer on prior approved versions (matched on name). This looks like a manual publish by a known maintainer rather than a publisher change. Recorded as INFO for audit trail.
v5.0.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.5
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.4
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.