@tryghost/mg-json
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): Ghost Foundation migrated to GitHub Actions CI publishing with SLSA attestation; stable pattern going forward. | ai | |
| provenance | missing-githead | AI (provenance): CI/CD publish via GitHub Actions with SLSA provenance replaces gitHead as the commit linkage mechanism. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Dormancy reflects the monorepo migration cadence, not account takeover; SLSA attestation confirms legitimate CI publish. | ai | |
| dependencies | unvetted-dep:@tryghost/mg-utils | AI (dependencies): First-party Ghost org dependency; stable pattern across this package's versions. | ai | |
| dependencies | unvetted-dep:node-email-verifier | AI (dependencies): Pinned to exact version 4.0.0; no advisories; consistent with package's email-processing purpose. | ai |
Versions (showing 18 of 18)
| Version | Deps | Published |
|---|---|---|
| 0.20.0 | 5 / 1 | |
| 0.19.3 | 5 / 1 | |
| 0.19.2 | 5 / 1 | |
| 0.19.1 | 5 / 1 | |
| 0.19.0 | 5 / 1 | |
| 0.18.0 | 5 / 1 | |
| 0.17.0 | 5 / 1 | |
| 0.16.0 | 5 / 1 | |
| 0.15.0 | 5 / 1 | |
| 0.14.0 | 5 / 1 | |
| 0.13.0 | 5 / 1 | |
| 0.12.0 | 5 / 1 | |
| 0.11.13 | 5 / 3 | |
| 0.11.12 | 5 / 3 | |
| 0.11.11 | 5 / 3 | |
| 0.11.10 | 5 / 3 | |
| 0.11.9 | 5 / 3 | |
| 0.11.8 | 5 / 3 |
v0.20.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.19.2
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.
v0.19.1
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.
v0.19.0
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.
v0.18.0
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.
v0.17.0
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.
v0.16.0
3 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.
This version was published by a different npm account than previous versions on 2026-04-06. 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.
v0.15.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.14.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.12.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.13
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.12
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.11.11
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.10
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.11.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.