@vpxa/aikit@0.1.411
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 guarded postinstall control-surface mutation creates lifecycle risk, but source inspection does not establish malicious behavior or a covert payload chain. Per policy, this is a warn-level same-vendor launcher migration.
Decision evidence
public snapshot- package.json runs bin/postinstall-managed-launcher.mjs at postinstall.
- bin/postinstall-managed-launcher.mjs conditionally imports the CLI and invokes migrate-launcher.
- packages/cli/dist/index.js migrates version-pinned user IDE MCP entries.
- packages/browser/dist/index.js can run npx -y agent-browser@latest on explicit browser launch.
- Postinstall is a no-op outside ~/.aikit/versions/v*-staging/package.
- Migration requires ~/.aikit/current-version.json and an existing matching version-pinned AI Kit entry.
- Migrator targets AI Kit launcher replacement, not arbitrary config entries.
- No credential harvesting, covert exfiltration, or destructive payload was found in inspected paths.
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.411.
See all versions of @vpxa/aikit for other recorded verdicts.
- Review the evidence and your use of @vpxa/aikit@0.1.411 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.