@tryghost/kg-default-atoms
`npm install @tryghost/kg-default-atoms --save`
Supply chain provenance
Status for the latest visible version.
Maintainers
Versions (showing 19 of 19)
| Version | Deps | Published |
|---|---|---|
| 5.2.3 | 0 / 13 | |
| 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 | |
| 5.1.0 | 0 / 2 | |
| 5.0.4 | 0 / 2 | |
| 5.0.3 | 0 / 2 | |
| 5.0.2 | 0 / 2 | |
| 5.0.1 | 0 / 2 | |
| 5.0.0 | 0 / 2 |
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.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. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.