@whoiskaushik/mandate@0.1.4
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe automatic install-time agent configuration and background proxy setup create a real agent extension lifecycle risk. The inspected proxy forwards requests to their upstream LLM, and the source reviewed does not establish unrelated data export or broader control hijacking.
Decision evidence
public snapshot- The npm postinstall hook automatically runs the package setup command.
- Setup writes this package’s MCP command into the user’s global Claude configuration and starts a local telemetry proxy.
- The proxy inspects agent request bodies and forwards requests to an upstream LLM; the inspected forwarding code does not establish export to an unrelated recipient.
- The configured MCP server launches this package’s own command, and the inspected source does not establish prompt or tool-content export to an external recipient.
Source & flagged code
5 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgThe npm postinstall hook automatically runs the package setup command.
package.jsonView on unpkg · L18Findings
Affected versions and remediation
This report applies to @whoiskaushik/mandate@0.1.4.
See all versions of @whoiskaushik/mandate for other recorded verdicts.
- Review the evidence and your use of @whoiskaushik/mandate@0.1.4 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.