gatsby-source-filesystem
Gatsby source plugin for building websites from local data. Markdown, JSON, images, YAML, CSV, and dozens of other data types supported.
Supply chain provenance
Status for the latest visible version.
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
Keywords
Accepted risks
Findings the reviewer chose to accept rather than block on.
| Source | Rule | Reason | Accepted by | When |
|---|---|---|---|---|
| provenance | publisher-changed | AI (provenance): Publisher change reflects Netlify's acquisition of Gatsby; serhalp-netlify is a verified Netlify employee with 5570 approved packages. This transition is organizational, not a takeover. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers mlgualtieri-gatsby and serhalp-netlify are Netlify employees taking over Gatsby maintenance post-acquisition. Legitimate organizational transition. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Removal of original Gatsby founders (kylemathews, dschau) is consistent with Netlify acquisition transition. Not indicative of malicious takeover. | ai | |
| phantom-deps | phantom-dep:mime | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:xstate | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:fs-extra | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:file-type | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:valid-url | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:pretty-bytes | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel runtime dependency; standard for Gatsby packages compiled with babel-preset-gatsby-package. | ai | |
| phantom-deps | phantom-dep:gatsby-core-utils | AI (phantom-deps): Declared runtime dependency; phantom detection likely due to compiled Babel output being distributed rather than source files. | ai |
Versions (showing 100 of 284)
| Version | Deps | Published |
|---|---|---|
| 5.16.0 | 9 / 4 | |
| 5.15.0 | 9 / 4 | |
| 5.14.0 | 9 / 4 | |
| 5.13.1 | 9 / 4 | |
| 5.13.0 | 9 / 4 | |
| 5.12.1 | 9 / 4 | |
| 5.12.0 | 9 / 4 | |
| 5.11.0 | 9 / 4 | |
| 5.10.0 | 9 / 4 | |
| 5.9.0 | 9 / 4 | |
| 5.8.0 | 9 / 4 | |
| 5.7.0 | 9 / 4 | |
| 5.6.0 | 9 / 4 | |
| 5.5.0 | 9 / 4 | |
| 5.4.0 | 10 / 4 | |
| 5.3.1 | 10 / 4 | |
| 5.3.0 | 10 / 4 | |
| 5.2.0 | 10 / 4 | |
| 5.1.0 | 10 / 4 | |
| 5.0.0 | 10 / 4 | |
| 4.25.0 | 10 / 4 | |
| 4.24.0 | 10 / 4 | |
| 4.23.0 | 10 / 4 | |
| 4.22.0 | 10 / 4 | |
| 4.21.1 | 11 / 4 | |
| 4.21.0 | 11 / 4 | |
| 4.20.0 | 12 / 4 | |
| 4.19.0 | 12 / 4 | |
| 4.18.1 | 12 / 4 | |
| 4.18.0 | 12 / 4 | |
| 4.17.0 | 12 / 4 | |
| 4.16.0 | 12 / 4 | |
| 4.15.0 | 12 / 4 | |
| 4.14.0 | 12 / 4 | |
| 4.13.0 | 12 / 4 | |
| 4.12.1 | 12 / 4 | |
| 4.12.0 | 12 / 4 | |
| 4.11.1 | 12 / 4 | |
| 4.11.0 | 12 / 4 | |
| 4.10.1 | 12 / 4 | |
| 4.10.0 | 12 / 4 | |
| 4.9.1 | 12 / 4 | |
| 4.9.0 | 12 / 4 | |
| 4.8.2 | 12 / 4 | |
| 4.8.1 | 12 / 4 | |
| 4.7.0 | 12 / 4 | |
| 4.6.0 | 13 / 4 | |
| 4.5.2 | 13 / 4 | |
| 4.5.0 | 13 / 4 | |
| 4.4.0 | 13 / 4 | |
| 4.2.0 | 13 / 4 | |
| 4.1.2 | 13 / 4 | |
| 4.1.1 | 13 / 4 | |
| 4.0.0 | 13 / 4 | |
| 3.15.0 | 13 / 4 | |
| 3.14.0 | 13 / 4 | |
| 3.13.0 | 13 / 5 | |
| 3.12.0 | 13 / 5 | |
| 3.11.0 | 13 / 5 | |
| 3.10.0 | 13 / 5 | |
| 3.9.0 | 13 / 5 | |
| 3.8.0 | 13 / 5 | |
| 3.7.1 | 13 / 5 | |
| 3.7.0 | 13 / 5 | |
| 3.6.0 | 13 / 5 | |
| 3.5.0 | 13 / 5 | |
| 3.4.0 | 13 / 5 | |
| 3.3.0 | 13 / 5 | |
| 3.2.0 | 13 / 5 | |
| 3.1.0 | 13 / 5 | |
| 3.0.0 | 13 / 5 | |
| 2.11.1 | 13 / 5 | |
| 2.11.0 | 13 / 5 | |
| 2.10.0 | 13 / 5 | |
| 2.9.1 | 13 / 5 | |
| 2.9.0 | 13 / 4 | |
| 2.8.1 | 13 / 4 | |
| 2.8.0 | 13 / 4 | |
| 2.7.0 | 13 / 4 | |
| 2.6.1 | 13 / 4 | |
| 2.6.0 | 13 / 4 | |
| 2.5.0 | 14 / 4 | |
| 2.4.2 | 14 / 4 | |
| 2.4.1 | 14 / 4 | |
| 2.4.0 | 14 / 4 | |
| 2.3.37 | 14 / 4 | |
| 2.3.36 | 14 / 4 | |
| 2.3.35 | 14 / 4 | |
| 2.3.34 | 14 / 4 | |
| 2.3.33 | 15 / 4 | |
| 2.3.32 | 15 / 4 | |
| 2.3.31 | 15 / 4 | |
| 2.3.30 | 15 / 4 | |
| 2.3.29 | 15 / 4 | |
| 2.3.28 | 15 / 4 | |
| 2.3.27 | 15 / 4 | |
| 2.3.26 | 15 / 4 | |
| 2.3.25 | 15 / 4 | |
| 2.3.24 | 15 / 4 | |
| 2.3.23 | 15 / 4 |
v5.16.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.14.0
2 findingsThis version was published by a different npm account than previous versions on 2024-11-06. 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.
v5.13.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.13.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-08-24. This could indicate a legitimate maintainer transition or an account compromise.
v5.11.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.10.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-04-18. This could indicate a legitimate maintainer transition or an account compromise.
v5.8.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-21. This could indicate a legitimate maintainer transition or an account compromise.
v5.6.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-02-07. This could indicate a legitimate maintainer transition or an account compromise.
v5.5.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-24. This could indicate a legitimate maintainer transition or an account compromise.
v5.4.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2023-01-10. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-14. This could indicate a legitimate maintainer transition or an account compromise.
v5.3.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-12-13. This could indicate a legitimate maintainer transition or an account compromise.
v5.2.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.1.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-22. This could indicate a legitimate maintainer transition or an account compromise.
v5.0.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-11-08. This could indicate a legitimate maintainer transition or an account compromise.
v4.25.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.24.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-27. This could indicate a legitimate maintainer transition or an account compromise.
v4.23.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-09-13. This could indicate a legitimate maintainer transition or an account compromise.
v4.22.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-30. This could indicate a legitimate maintainer transition or an account compromise.
v4.21.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.21.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-16. This could indicate a legitimate maintainer transition or an account compromise.
v4.20.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-08-02. This could indicate a legitimate maintainer transition or an account compromise.
v4.19.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-19. This could indicate a legitimate maintainer transition or an account compromise.
v4.18.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.18.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-07-05. This could indicate a legitimate maintainer transition or an account compromise.
v4.17.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-21. This could indicate a legitimate maintainer transition or an account compromise.
v4.16.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-06-07. This could indicate a legitimate maintainer transition or an account compromise.
v4.15.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-24. This could indicate a legitimate maintainer transition or an account compromise.
v4.14.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-05-10. This could indicate a legitimate maintainer transition or an account compromise.
v4.13.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-26. This could indicate a legitimate maintainer transition or an account compromise.
v4.12.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v4.12.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-04-12. This could indicate a legitimate maintainer transition or an account compromise.
v4.11.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.11.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-29. This could indicate a legitimate maintainer transition or an account compromise.
v4.10.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-16. This could indicate a legitimate maintainer transition or an account compromise.
v4.9.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-09. This could indicate a legitimate maintainer transition or an account compromise.
v4.9.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.8.2
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-03-01. This could indicate a legitimate maintainer transition or an account compromise.
v4.8.1
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-25. This could indicate a legitimate maintainer transition or an account compromise.
v4.7.0
2 findingsPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
[Accepted risk] This version was published by a different npm account than previous versions on 2022-02-08. This could indicate a legitimate maintainer transition or an account compromise.
v4.6.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.5.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.5.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.4.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.2.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.1.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.0.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.