@grovetech/defender@0.33.0
Active runtime protection for vibe-coded apps — drops in as Express middleware (web + AI layer), blocks prompt injection, PII leaks, and sensitive paths in real time. By Grovetech AI.
AI Security Review
scanned 3d ago · by lpm-firewall-aiThe default runtime telemetry includes the machine hostname, an identifying detail, in POSTs to the vendor endpoint. The API-key flow flagged in the CLI is scoped to an explicit replay command and targets Grovetech’s own service, so the evidence supports a telemetry warning rather than malicious credential exfiltration.
Decision evidence
public snapshot- Creating a Defender instance reads the machine hostname and passes it into the telemetry client.
- Runtime telemetry posts the hostname, version, request count, and events to its configured endpoint; the instance starts a periodic flush timer by default.
- The replay command sends the Defender API key to Grovetech’s own API and runs only when the user invokes `defender replay`.
- Telemetry sanitizes event excerpts and payload text, including masking detected secrets.
Source & flagged code
8 flaggedPackage text addresses the security reviewer or scanner and tries to influence the review outcome.
README.mdView on unpkgSource appears to send environment or credential material to an external endpoint.
dist/esm/cli.jsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @grovetech/defender@0.33.0.
See all versions of @grovetech/defender for other recorded verdicts.
- Review the evidence and your use of @grovetech/defender@0.33.0 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.