@grovetech/defender
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.
This report shows the evidence for @grovetech/defender@0.33.2. 0 of 14 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential flows use Defender-specific keys with the package’s own service for its advertised protection and replay features. The manifest’s lifecycle script is a build-only `prepublishOnly` hook, and the README search did not substantiate the reviewer-manipulation hint.
Decision evidence
public snapshot- The package exports its library entry points and a separate CLI; `prepublishOnly` builds the package rather than running an install hook.
- The library takes its API key from explicit configuration or Defender-specific environment variables and uses a configurable Defender endpoint.
- The CLI sends the Defender key to the Defender service only in the `replay` command, which requires an attack ID and is selected by the user.
- Runtime telemetry posts Defender events to its configured endpoint with the Defender API key; this matches the package’s advertised runtime protection and reporting purpose.
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.2.
The versions list below shows the verdict for each recorded version.
- Review the evidence and your use of @grovetech/defender@0.33.2 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.