gatsby-plugin-sharp
2
Versions
—
License
No
Install Scripts
Missing
Provenance
Supply chain provenance
Status for the latest visible version.
No SLSA provenance
npm registry signatures
gitHead linked
Without SLSA provenance there is no cryptographic link between this tarball and the public source — the axios compromise (March 2026) relied on exactly this gap.
Maintainers
piehkathmbeckserhalp-netlifymlgualtieri-gatsbyfktylerbarnesdaniellewgatsby
Keywords
gatsbygatsby-pluginimagesharp
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): Gatsby monorepo package; mass-production flag is a false positive for the gatsbyjs org's many packages. | ai | |
| phantom-deps | phantom-dep:async | AI (phantom-deps): Declared dep used in compiled output; phantom-dep heuristic is a false positive for this transpiled package. | ai | |
| phantom-deps | phantom-dep:semver | AI (phantom-deps): Same as above — transpiled package, stable false positive. | ai | |
| phantom-deps | phantom-dep:bluebird | AI (phantom-deps): Same as above — transpiled package, stable false positive. | ai | |
| semgrep | semgrep:child-process-import | AI (semgrep): safe-sharp.js child_process usage is a documented Gatsby pattern for subprocess isolation; stable across versions. | ai | |
| phantom-deps | phantom-dep:probe-image-size | AI (phantom-deps): Same as above — transpiled package, stable false positive. | ai | |
| phantom-deps | phantom-dep:gatsby-plugin-utils | AI (phantom-deps): Same as above — transpiled package, stable false positive. | ai | |
| phantom-deps | phantom-dep:filenamify | AI (phantom-deps): Same as above — transpiled package, stable false positive. | ai |
v5.16.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v5.15.0
1 finding
LOW
No provenance attestation
provenance
Package was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.