@vpxa/aikit@0.1.402
Local-first AI developer toolkit — knowledge base, code analysis, context management, and developer tools for LLM agents
AI Security Review
scanned 3mo ago · by lpm-firewall-aiNo concrete malicious chain was found, but unattended self-update plus install-time MCP configuration migration is risky enough to warn. The postinstall guard prevents a publish block under the stated policy.
Decision evidence
public snapshot- package.json runs a postinstall hook.
- Postinstall imports CLI only in ~/.aikit version-staging installs.
- CLI migrates version-pinned MCP IDE configs automatically.
- Runtime updater fetches and installs newer npm releases.
- Postinstall is a narrow managed-staging guard and otherwise exits.
- Migration targets existing AI Kit entries, not arbitrary agent configs.
- No credential harvesting or unrelated exfiltration found.
- Registry network use is package update functionality.
Source & flagged code
13 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgPackage source references child process execution.
packages/tools/dist/index.jsView on unpkg · L1Findings
Affected versions and remediation
This report applies to @vpxa/aikit@0.1.402.
See all versions of @vpxa/aikit for other recorded verdicts.
- Review the evidence and your use of @vpxa/aikit@0.1.402 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.