@hashbrownai/react@0.8.3
React components for Hashbrown AI
AI Security Review
scanned 9d ago · by lpm-firewall-aiThe automatic telemetry is an installation privacy consideration, but source inspection ties its default recipient to the package’s own Hashbrown domain and limits repository hints to the consumer checkout. The runtime entrypoints and inspected parser dependencies showed no separate attack behavior.
Decision evidence
public snapshot- The postinstall hook collects an installation event; the event may include Git identity outside CI, and the collector sends it to the default hashbrown.dev endpoint.
- The package identifies hashbrown.dev as its homepage and identifies its repository as the Hashbrown React package, supporting that the telemetry recipient is package-aligned.
- The runtime entrypoints expose React and Hashbrown functionality, while the two inspected dependencies are parser libraries; no separate attack behavior was identified in those paths.
- Telemetry can be disabled through supported opt-out variables. Git identity is bounded, and repository hints are derived only from the consuming checkout’s local remote.
- The endpoint override accepts only loopback hosts; other values resolve to the package-aligned default endpoint.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe postinstall hook collects an installation event; the event may include Git identity outside CI, and the collector sends it to the default hashbrown.dev endpoint.
package.jsonView on unpkg · L63Findings
Affected versions and remediation
This report applies to @hashbrownai/react@0.8.3.
See all versions of @hashbrownai/react for other recorded verdicts.
- Review the evidence and your use of @hashbrownai/react@0.8.3 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.