gatsby-core-theme@44.35.13
Gatsby Theme NPM Package
AI Security Review
scanned 28d ago · by lpm-firewall-aiThe tracker actively forwards the complete incoming cookie object to an operator-configured endpoint, creating conditional credential exposure. The newsletter flow is consistent with signup behavior and does not append submitted identity fields to its success redirect.
Decision evidence
public snapshot- The server-side tracker parses the incoming Cookie header and places the parsed cookies into tracking parameters.
- The tracker serializes the full cookie object and sends the parameters to the operator-configured tracking API URL, without a destination allowlist in the inspected path.
- The SSR tracker invokes this logic while handling server data requests.
- The newsletter sends submitted signup fields to its signup endpoint; its redirect is gated on a successful response and does not append those fields.
- The manifest points to index.js and contains no install lifecycle hooks.
Source & flagged code
6 flaggedPackage source references dynamic require/import behavior.
__mocks__/gatsby.jsView on unpkg · L1Source redirects browser users to an external URL carrying identity material.
src/components/molecules/newsletter/form/index.jsView on unpkg · L29Findings
Affected versions and remediation
This report applies to gatsby-core-theme@44.35.13.
See all versions of gatsby-core-theme for other recorded verdicts.
- Review the evidence and your use of gatsby-core-theme@44.35.13 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.