@tryghost/mg-assetscraper-db
Downloads remote assets from Ghost migration data and replaces URLs with local Ghost paths.
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 |
|---|---|---|---|---|
| bogus-package | bogus-package | AI (bogus-package): Legitimate Ghost Foundation scoped package; sparse metadata is a style choice, not spam. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Same org context; removal paired with org-scoped additions is routine team rotation. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Ghost org accounts; consistent with internal team growth for this org-scoped package. | ai | |
| phantom-deps | phantom-dep:asakadb | AI (phantom-deps): asakadb is a declared runtime dep used via config/indirect import; consistent with this package's DB abstraction pattern. | ai | |
| phantom-deps | phantom-dep:cheerio | AI (phantom-deps): cheerio is a declared runtime dep; phantom-dep heuristic fires due to indirect/config usage in this scraper package. | ai | |
| phantom-deps | phantom-dep:sqlite3 | AI (phantom-deps): sqlite3 is a declared runtime dep used as sequelize dialect driver; indirect import is expected. | ai | |
| phantom-deps | phantom-dep:uuid | AI (phantom-deps): Ghost monorepo package; uuid is a declared dep used transitively or in build config, not a real phantom risk. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Ghost monorepo package; fs-extra is a declared dep used transitively or in build config, not a real phantom risk. | ai | |
| phantom-deps | phantom-dep:@tryghost/debug | AI (phantom-deps): Same org scope; declared dep from Ghost Foundation, stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/listr-smart-renderer | AI (phantom-deps): Same-org dep likely re-exported or used indirectly; stable false positive for this package. | ai | |
| phantom-deps | phantom-dep:@tryghost/mg-fs-utils | AI (phantom-deps): Same-org dep likely re-exported or used indirectly; stable false positive for this package. | ai |
Versions (showing 16 of 16)
| Version | Deps | Published |
|---|---|---|
| 0.11.0 | 8 / 7 | |
| 0.10.3 | 8 / 7 | |
| 0.10.2 | 8 / 7 | |
| 0.10.1 | 11 / 11 | |
| 0.10.0 | 11 / 11 | |
| 0.9.0 | 11 / 11 | |
| 0.6.0 | 11 / 11 | |
| 0.4.0 | 11 / 9 | |
| 0.3.2 | 13 / 9 | |
| 0.3.1 | 13 / 9 | |
| 0.2.8 | 14 / 11 | |
| 0.2.7 | 14 / 11 | |
| 0.2.6 | 14 / 11 | |
| 0.2.5 | 16 / 11 | |
| 0.2.2 | 16 / 11 | |
| 0.2.1 | 16 / 11 |
v0.11.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.3
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.2
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.1
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.10.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.9.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.6.0
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v0.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.3.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.8
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.7
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.6
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v0.2.5
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v0.2.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.