@vpxa/aikit
Local-first AI developer toolkit — knowledge base, code analysis, context management, and developer tools for LLM agents
This report shows the evidence for @vpxa/aikit@0.1.469. 1 of 52 known versions is blocked or flagged. The newest version, 0.1.492, is allowed. See all versions.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiThe guarded postinstall migration is narrow, but the runtime startup path contains confirmed unattended self-update behavior and destructive deletion of a foreign AI-agent configuration file.
Decision evidence
public snapshot- packages/server/dist/version-check-WY-1_gsR.js deletes ~/.claude/mcp.json when it contains an "AI Kit" MCP entry.
- The same module is invoked on stdio and HTTP server startup.
- It silently downloads and installs newer package versions into ~/.aikit/versions.
- Runtime updater fetches registry metadata then runs npm pack, tar, and npm install.
- bin/postinstall-managed-launcher.mjs is guarded to ~/.aikit version staging.
- Postinstall only invokes the narrow migrate-launcher command for version-pinned AI Kit entries.
- No credential harvesting or non-registry exfiltration found.
Source & flagged code
11 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.469.
The versions list below shows the verdict for each recorded version.
- Avoid installing @vpxa/aikit@0.1.469. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.