@tryghost/image-transform
`npm install @tryghost/image-transform --save`
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 | no-provenance | AI (provenance): Ghost SDK packages historically published without Sigstore provenance; stable pattern for this package. | ai | |
| dependencies | unvetted-dep:@tryghost/errors | AI (dependencies): First-party Ghost Foundation dependency; stable across all versions of this package. | ai |
Versions (showing 9 of 9)
| Version | Deps | Published |
|---|---|---|
| 1.4.15 | 2 / 4 | |
| 1.4.14 | 2 / 4 | |
| 1.4.10 | 2 / 4 | |
| 1.4.9 | 3 / 4 | |
| 1.4.8 | 3 / 4 | |
| 1.4.4 | 3 / 4 | |
| 1.4.3 | 3 / 4 | |
| 1.4.2 | 2 / 4 | |
| 1.4.1 | 3 / 4 |
v1.4.15
1 findingPublished via CI/CD with Sigstore attestation (predicate: https://slsa.dev/provenance/v1). This is the strongest supply chain integrity signal.
v1.4.10
2 findingsThis version was published by a different npm account than previous versions on 2026-01-12. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.9
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.8
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.4
2 findingsThis version was published by a different npm account than previous versions on 2025-05-25. This could indicate a legitimate maintainer transition or an account compromise.
Package was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v1.4.3
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v1.4.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.