@aspectlylabs/mikka@0.0.293
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 scripts, and the flagged credential flow is a per-run broker that targets official provider endpoints by default or an explicitly configured HTTPS provider. The reviewed hosted runner proxies through that broker and rejects provider tokens in its environment.
Decision evidence
public snapshot- The manifest describes a local daemon that runs agents through the user's own CLIs and exposes its CLI and library entry points; it defines no lifecycle scripts.
- The model-key broker defaults to api.anthropic.com or api.openai.com and limits requests to provider API paths.
- Custom provider URLs must use HTTPS and cannot contain embedded credentials, queries, or fragments.
- The broker attaches the model key to requests sent to the selected provider endpoint; redirects are rejected.
- The hosted runner rejects provider keys in its environment and routes model traffic through the local broker socket.
- The CLI's production service URL is app.aspectlylabs.com/mikka, consistent with the package's own service.
Source & flagged code
6 flaggedPackage source references child process execution.
github-credentials.mjsView on unpkg · L4Findings
Affected versions and remediation
This report applies to @aspectlylabs/mikka@0.0.293.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.293 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.