gatsby-plugin-page-creator
Gatsby plugin that automatically creates pages from React components in specified directories
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 |
|---|---|---|---|---|
| source-diff | source-size-dropped | AI (source-diff): Source size drop reflects Babel transpilation output (src/ → index.js); expected for compiled plugins. | ai | |
| phantom-deps | phantom-dep:fs-exists-cached | AI (phantom-deps): Utility dependency used by Gatsby plugins; indirect import pattern is stable for this package. | ai | |
| phantom-deps | phantom-dep:gatsby-telemetry | AI (phantom-deps): Gatsby ecosystem dependency; indirect import via Gatsby framework is expected for plugins. | ai | |
| phantom-deps | phantom-dep:gatsby-core-utils | AI (phantom-deps): Gatsby ecosystem dependency; indirect import via Gatsby framework is expected for plugins. | ai | |
| phantom-deps | phantom-dep:gatsby-page-utils | AI (phantom-deps): Gatsby ecosystem dependency; indirect import via Gatsby framework is expected for plugins. | ai | |
| phantom-deps | phantom-dep:gatsby-plugin-utils | AI (phantom-deps): Gatsby ecosystem dependency; indirect import via Gatsby framework is expected for plugins. | ai | |
| phantom-deps | phantom-dep:@sindresorhus/slugify | AI (phantom-deps): Legitimate utility dependency for slug generation; indirect import pattern is normal for plugins. | ai | |
| phantom-deps | phantom-dep:globby | AI (phantom-deps): Globby is legitimately used by this Gatsby plugin for file globbing; indirect import pattern is normal for plugins. | ai | |
| phantom-deps | phantom-dep:lodash | AI (phantom-deps): Lodash is a legitimate utility dependency used by Gatsby plugins; indirect import pattern is expected. | ai | |
| phantom-deps | phantom-dep:chokidar | AI (phantom-deps): Chokidar is used for file watching in this page-creator plugin; indirect import is normal for this use case. | ai | |
| phantom-deps | phantom-dep:@babel/runtime | AI (phantom-deps): Framework-scoped Babel package loaded by convention; expected for Babel-compiled plugins. | ai | |
| provenance | publisher-changed | AI (provenance): Gatsby maintenance transitioned to Netlify staff; pieh → serhalp-netlify is a known organizational change. | ai | |
| maintainer-change | maintainer-added | AI (maintainer-change): New maintainers are Netlify-affiliated staff taking over Gatsby maintenance. | ai | |
| maintainer-change | maintainer-removed | AI (maintainer-change): Old Gatsby maintainers removed as part of known org transition to Netlify. | ai | |
| bogus-package | bogus-package | AI (bogus-package): Templated names are expected for gatsby-* monorepo packages; empty index.js is standard Gatsby plugin convention. | ai | |
| dependencies | unvetted-dep:fs-exists-cached | AI (dependencies): fs-exists-cached is a long-standing stable utility used throughout the Gatsby ecosystem; no malicious behavior associated with it. | ai | |
| phantom-deps | phantom-dep:@babel/traverse | AI (phantom-deps): @babel/traverse is explicitly listed as a direct dependency in package.json; the phantom-dep finding reflects framework-convention loading, not a missing or suspicious dependency. | ai |
Versions (showing 51 of 196)
| Version | Deps | Published |
|---|---|---|
| 5.16.0 | 11 / 4 | |
| 5.15.0 | 11 / 4 | |
| 5.14.0 | 11 / 4 | |
| 5.13.1 | 12 / 4 | |
| 5.13.0 | 12 / 4 | |
| 5.12.3 | 12 / 4 | |
| 5.12.2 | 12 / 4 | |
| 5.12.1 | 12 / 4 | |
| 5.12.0 | 12 / 4 | |
| 5.11.0 | 12 / 4 | |
| 5.10.0 | 12 / 4 | |
| 5.9.0 | 12 / 4 | |
| 5.8.0 | 12 / 4 | |
| 5.7.0 | 12 / 4 | |
| 5.6.0 | 12 / 4 | |
| 5.5.0 | 12 / 4 | |
| 5.4.0 | 12 / 4 | |
| 5.3.1 | 12 / 4 | |
| 5.3.0 | 12 / 4 | |
| 5.2.0 | 12 / 4 | |
| 5.1.0 | 12 / 4 | |
| 5.0.0 | 12 / 4 | |
| 4.25.0 | 12 / 4 | |
| 4.24.1 | 12 / 4 | |
| 4.24.0 | 12 / 4 | |
| 4.23.1 | 12 / 4 | |
| 4.23.0 | 12 / 4 | |
| 4.22.0 | 12 / 4 | |
| 4.21.0 | 12 / 4 | |
| 4.20.0 | 12 / 4 | |
| 4.19.0 | 11 / 4 | |
| 4.18.1 | 11 / 4 | |
| 4.18.0 | 11 / 4 | |
| 4.17.0 | 11 / 4 | |
| 4.16.0 | 11 / 4 | |
| 4.15.1 | 11 / 4 | |
| 4.15.0 | 11 / 4 | |
| 4.14.1 | 11 / 4 | |
| 4.14.0 | 11 / 4 | |
| 4.13.0 | 11 / 4 | |
| 4.12.1 | 11 / 4 | |
| 4.12.0 | 11 / 4 | |
| 4.11.1 | 11 / 4 | |
| 4.11.0 | 11 / 4 | |
| 4.10.2 | 11 / 4 | |
| 4.10.1 | 11 / 4 | |
| 4.10.0 | 11 / 4 | |
| 4.9.1 | 11 / 4 | |
| 4.9.0 | 11 / 4 | |
| 4.8.2 | 11 / 4 | |
| 4.8.1 | 11 / 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.3
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v5.12.2
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
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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
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-25. This could indicate a legitimate maintainer transition or an account compromise.
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.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-10-10. This could indicate a legitimate maintainer transition or an account compromise.
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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
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.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.1
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.15.0
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.14.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-05-16. 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.2
1 findingPackage was published without Sigstore provenance. Consider requesting the maintainer enable provenance via CI/CD.
v4.10.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.10.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.9.0
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.2
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.
v4.8.1
1 findingPackage was published without Sigstore provenance. Only ~12% of npm packages have provenance, so this is common but not ideal.