@aspectlylabs/mikka@0.0.337
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install lifecycle hooks, and the flagged credential flows are tied to user-started agent runs and configured services. The reviewed source routes keys through constrained brokers rather than redirecting them to a fixed unrelated gateway.
Decision evidence
public snapshot- The manifest exposes a daemon CLI and library entry points and declares no lifecycle scripts.
- API keys are routed through a broker to the configured HTTPS provider or the matching Anthropic/OpenAI default endpoint.
- The broker is created for an assigned run and forwards requests through that broker; the native runner uses its mounted broker socket.
- GitHub credentials are exchanged at a configured run endpoint and used by the GitHub CLI for authorized repository operations.
Source & flagged code
6 flaggedPackage source references child process execution.
github-credentials.mjsView on unpkg · L7Findings
Affected versions and remediation
This report applies to @aspectlylabs/mikka@0.0.337.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.337 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.