@tryghost/mg-assetscraper
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): Expected side-effect of switching to CI-based publishing with attestation. | ai | |
| provenance | publisher-changed | AI (provenance): Manual→CI/CD attested transition for official TryGhost package; provenance improved. | ai | |
| phantom-deps | phantom-dep:listr | AI (phantom-deps): listr used as CLI runner, not directly imported; benign for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/logging | AI (phantom-deps): Same-org first-party logging dep, not a risk indicator. | ai |
Versions (showing 22 of 22)
| Version | Deps | Published |
|---|---|---|
| 0.8.0 | 13 / 2 | |
| 0.7.0 | 13 / 2 | |
| 0.6.0 | 13 / 2 | |
| 0.5.0 | 13 / 2 | |
| 0.4.37 | 13 / 2 | |
| 0.4.36 | 13 / 2 | |
| 0.4.35 | 13 / 2 | |
| 0.4.34 | 13 / 4 | |
| 0.4.33 | 13 / 4 | |
| 0.4.32 | 13 / 4 | |
| 0.4.31 | 13 / 4 | |
| 0.4.30 | 13 / 4 | |
| 0.4.29 | 13 / 4 | |
| 0.4.28 | 13 / 4 | |
| 0.4.27 | 13 / 4 | |
| 0.4.26 | 13 / 4 | |
| 0.4.21 | 13 / 4 | |
| 0.4.19 | 13 / 4 | |
| 0.4.18 | 13 / 4 | |
| 0.4.17 | 13 / 4 | |
| 0.4.16 | 13 / 4 | |
| 0.4.15 | 13 / 4 |
v0.8.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.7.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-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.
v0.6.0
2 findingsThis version was published by a different npm account than previous versions on 2026-04-04. 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.5.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.37
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.36
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.35
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.34
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.33
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.32
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.31
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.30
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.29
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.28
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.27
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.26
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.21
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.19
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.18
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.17
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.4.16
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.4.15
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.