@tryghost/mg-wp-xml
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 | missing-githead | AI (provenance): SLSA provenance attestation present; Ghost org publishes via GitHub Actions CI/CD which may not set gitHead. | ai | |
| npm-metadata | no-description | AI (npm-metadata): Ghost Foundation scoped package; missing description is a cosmetic issue, not a risk indicator. | ai | |
| dependencies | unvetted-dep:markdown-it | AI (dependencies): markdown-it is a well-established, widely-used Markdown parser; stable false positive for this package. | ai | |
| provenance | no-provenance | AI (provenance): Ghost Foundation monorepo package; no provenance is consistent across all versions of this package family. | ai |
Versions (showing 45 of 45)
| Version | Deps | Published |
|---|---|---|
| 0.17.2 | 8 / 0 | |
| 0.17.1 | 8 / 0 | |
| 0.17.0 | 8 / 0 | |
| 0.16.0 | 8 / 0 | |
| 0.15.0 | 8 / 0 | |
| 0.14.3 | 8 / 0 | |
| 0.14.0 | 8 / 0 | |
| 0.13.0 | 8 / 0 | |
| 0.12.0 | 8 / 0 | |
| 0.11.0 | 8 / 0 | |
| 0.10.0 | 8 / 0 | |
| 0.9.0 | 7 / 0 | |
| 0.8.0 | 7 / 0 | |
| 0.7.0 | 7 / 0 | |
| 0.5.21 | 6 / 2 | |
| 0.5.20 | 6 / 2 | |
| 0.5.19 | 6 / 2 | |
| 0.5.18 | 6 / 2 | |
| 0.5.16 | 6 / 2 | |
| 0.5.15 | 6 / 2 | |
| 0.5.14 | 6 / 2 | |
| 0.5.13 | 6 / 2 | |
| 0.5.11 | 6 / 2 | |
| 0.5.10 | 6 / 2 | |
| 0.5.8 | 6 / 2 | |
| 0.5.7 | 6 / 2 | |
| 0.5.6 | 6 / 2 | |
| 0.5.5 | 6 / 2 | |
| 0.5.4 | 6 / 2 | |
| 0.5.3 | 6 / 2 | |
| 0.5.2 | 6 / 2 | |
| 0.5.1 | 6 / 2 | |
| 0.5.0 | 6 / 2 | |
| 0.4.9 | 6 / 2 | |
| 0.4.8 | 6 / 2 | |
| 0.4.7 | 6 / 2 | |
| 0.4.6 | 6 / 2 | |
| 0.4.5 | 6 / 2 | |
| 0.4.4 | 6 / 2 | |
| 0.4.3 | 6 / 2 | |
| 0.4.2 | 6 / 2 | |
| 0.4.1 | 6 / 2 | |
| 0.4.0 | 7 / 2 | |
| 0.3.28 | 6 / 2 | |
| 0.3.27 | 6 / 2 |
v0.17.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.17.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.5.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.5.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.9
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.8
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.7
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.6
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.5
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.4
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.3
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.2
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.1
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.0
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 finding[Accepted risk] Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 finding[Accepted risk] Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.