@tryghost/mg-curated-export
tbc
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 | slsa-provenance | AI (provenance): Ghost Foundation publishes via GitHub Actions with Sigstore attestation; stable pattern for this org. | ai | |
| phantom-deps | phantom-dep:cheerio | AI (phantom-deps): cheerio is declared in dependencies and used in the package; phantom-dep heuristic is a false positive here. | ai | |
| publish-pattern | dormant-publish | AI (publish-pattern): Ghost Foundation org package with SLSA attestation; dormancy reflects org publish cadence, not takeover. | ai |
Versions (showing 31 of 31)
| Version | Deps | Published |
|---|---|---|
| 0.13.2 | 4 / 1 | |
| 0.13.1 | 4 / 1 | |
| 0.13.0 | 4 / 1 | |
| 0.12.0 | 4 / 1 | |
| 0.11.0 | 4 / 1 | |
| 0.10.3 | 4 / 1 | |
| 0.10.1 | 5 / 1 | |
| 0.10.0 | 5 / 1 | |
| 0.7.0 | 3 / 1 | |
| 0.6.0 | 3 / 1 | |
| 0.5.0 | 3 / 1 | |
| 0.4.0 | 3 / 1 | |
| 0.3.44 | 3 / 1 | |
| 0.3.43 | 3 / 1 | |
| 0.3.42 | 3 / 3 | |
| 0.3.41 | 3 / 3 | |
| 0.3.40 | 3 / 3 | |
| 0.3.39 | 3 / 3 | |
| 0.3.38 | 3 / 3 | |
| 0.3.37 | 3 / 3 | |
| 0.3.36 | 3 / 3 | |
| 0.3.35 | 3 / 3 | |
| 0.3.34 | 3 / 3 | |
| 0.3.33 | 3 / 3 | |
| 0.3.32 | 3 / 3 | |
| 0.3.31 | 3 / 3 | |
| 0.3.30 | 3 / 3 | |
| 0.3.29 | 3 / 3 | |
| 0.3.28 | 3 / 3 | |
| 0.3.27 | 3 / 3 | |
| 0.3.26 | 3 / 3 |
v0.13.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.13.1
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 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.3.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.32
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.31
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.30
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.29
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.28
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.27
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.3.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.