@whoiskaushik/mandate@0.1.6
AI Security Review
scanned 1d ago · by lpm-firewall-aiSource inspection confirms automatic agent configuration changes and a detached proxy launched by postinstall. The inspected behavior is first-party package-owned setup, so it warrants a warning rather than a block.
Decision evidence
public snapshot- The postinstall hook automatically runs the setup command.
- Setup writes the package’s MCP entry to the project’s Antigravity config and the user’s global Claude config without a consent check.
- Setup starts a detached local telemetry proxy.
- The registered MCP server exposes Mandate governance tools; inspected source does not show it collecting prompts or credentials.
- The MCP server is package-owned and its listed tools concern Mandate status, model switches, and action checks.
- The proxy is started on a loopback address; inspected setup code does not send installation data to an external collector.
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 postinstall hook automatically runs the setup command.
package.jsonView on unpkg · L19Findings
Affected versions and remediation
This report applies to @whoiskaushik/mandate@0.1.6.
See all versions of @whoiskaushik/mandate for other recorded verdicts.
- Review the evidence and your use of @whoiskaushik/mandate@0.1.6 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.