@hashbrownai/anthropic
Anthropic provider for Hashbrown AI
This report shows the evidence for @hashbrownai/anthropic@0.8.1. 1 of 8 known versions is blocked or flagged. The newest version, 0.8.3, is flagged. See all versions.
AI Security Review
scanned 11d ago · by lpm-firewall-aiSource confirms automatic postinstall disclosure of identifying installation and environment data to a publisher-selected endpoint, with no affirmative consent gate. This is a concrete install-time attack surface and warrants blocking publication.
Decision evidence
public snapshot- package.json runs a postinstall script that invokes the collector.
- The collector sends an automatic package-installed event with installation, package, host, runtime, and environment details to hashbrown.dev by default.
- The event can include saved global Git name and email, plus checkout repository details.
- The install collector sends the event unless telemetry is disabled or debug logging is enabled; only loopback endpoint overrides are accepted.
- The helper reuses a valid installation UUID from the user's ~/.hashbrown/installation-id file or creates a UUID and writes it to a temporary file.
- An opt-out is available through telemetry environment variables, and debug mode logs the event instead of sending it.
- The install event has a short deadline and does not fail installation if collection or transport fails.
Source & flagged code
7 flaggedPackage defines install-time lifecycle scripts.
package.jsonView on unpkgpackage.json runs a postinstall script that invokes the collector.
package.jsonView on unpkg · L37Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @hashbrownai/anthropic@0.8.1.
The versions list below shows the verdict for each recorded version.
- Avoid installing @hashbrownai/anthropic@0.8.1. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.