@vpxa/aikit@0.1.478
Local-first AI developer toolkit — knowledge base, code analysis, context management, and developer tools for LLM agents
AI Security Review
scanned 3d ago · by lpm-firewall-aiSource inspection shows a narrowly gated managed-install compatibility migration and no confirmed attack behavior. Scanner similarity labels and generic runtime primitives did not establish malicious activity in the inspected excerpts.
Decision evidence
public snapshot- package.json runs a postinstall launcher migration; its guard limits it to a versioned staging package under the managed .aikit directory and requires the managed version pointer.
- The launcher imports that staging copy of the CLI and invokes migrate-launcher. The migration reads user-scope IDE configs and replaces existing AI Kit entries that are legacy, stale, or version-pinned.
- The inspected agent integration locations describe IDE detection, config paths, scaffold update strategies, existing instruction-file targets, and generated AI Kit tool guidance.
- The remaining cited modules show a dashboard MCP request, proxy stream handling, a browser request wrapper, embedding utilities, and exported code-analysis tools; these excerpts establish no attack behavior.
Source & flagged code
18 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgA bounded semantic-analysis stage reached its safety limit; remaining detectors completed, but this package requires AI review.
package.jsonView on unpkgFindings
Affected versions and remediation
This report applies to @vpxa/aikit@0.1.478.
See all versions of @vpxa/aikit for other recorded verdicts.
- Review the evidence and your use of @vpxa/aikit@0.1.478 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.