@vpxa/aikit@0.1.382
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-aiSource confirms a guarded same-vendor MCP launcher migration rather than a malicious chain. The install-time configuration mutation is still a lifecycle risk warranting a warning.
Decision evidence
public snapshot- package.json runs postinstall.
- bin/postinstall-managed-launcher.mjs imports CLI during a guarded managed update.
- packages/cli/dist/index.js migrates existing IDE MCP entries, including Claude/Codex-related configs.
- packages/browser/dist/index.js can run npx to download agent-browser on explicit browser use.
- Postinstall is a no-op outside ~/.aikit/versions/v*-staging/package.
- Migration requires ~/.aikit/current-version.json and a version-pinned existing AI Kit entry.
- Postinstall contains no network, credential harvesting, or shell execution.
- Registry requests target npm only and occur in explicit update/runtime features.
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.382.
See all versions of @vpxa/aikit for other recorded verdicts.
- Review the evidence and your use of @vpxa/aikit@0.1.382 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.