@vpxa/aikit@0.1.405
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-aiThe lifecycle mutation is guarded and package-aligned rather than a broad foreign-agent hijack, but its AI-agent config migration and runtime self-updater are meaningful extension-lifecycle risk.
Decision evidence
public snapshot- package.json runs postinstall.
- bin/postinstall-managed-launcher.mjs conditionally imports CLI during managed staging installs.
- packages/cli/dist/index.js migrates matching AI Kit MCP configurations.
- packages/server/dist/startup-maintenance-QrloHssd.js checks npm and can install newer versions at runtime.
- Postinstall is a no-op outside ~/.aikit/versions/v*-staging/package.
- Migration only replaces version-pinned AI Kit MCP entries with its launcher.
- No credential harvesting or unrelated endpoint exfiltration found.
- Registry traffic is limited to @vpxa/aikit npm metadata/tarballs.
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.405.
See all versions of @vpxa/aikit for other recorded verdicts.
- Review the evidence and your use of @vpxa/aikit@0.1.405 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.