gatsby-core-theme@44.35.7
Gatsby Theme NPM Package
AI Security Review
scanned 2mo ago · by lpm-firewall-aiSource inspection found no lifecycle execution, credential harvesting, shell execution, payload loading, or persistence. The scanner hit is a user-facing newsletter flow and consent-gated site analytics, not a concrete malicious chain.
Decision evidence
public snapshot- Manifest has no npm lifecycle hooks; only test and Storybook scripts.
- Newsletter IP lookup runs in the rendered React component.
- Newsletter submission sends entered fields to its named subscription endpoint and redirects only after an OK response.
- Analytics loading is guarded by consent-category checks and environment flags.
- Build-time file writes generate site artifacts, not host persistence.
- Newsletter includes the visitor IP and entered contact fields in a third-party GET request.
- Browser entrypoint can load configured third-party analytics scripts.
Source & flagged code
4 flaggedSource redirects browser users to an external URL carrying identity material.
src/components/molecules/newsletter/form/index.jsView on unpkg · L29Newsletter IP lookup runs in the rendered React component.
src/components/molecules/newsletter/form/index.jsView on unpkg · L29Findings
Affected versions and remediation
This report applies to gatsby-core-theme@44.35.7.
See all versions of gatsby-core-theme for other recorded verdicts.
- Review the evidence and your use of gatsby-core-theme@44.35.7 before allowing it. Restrict the permissions described in this report.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.