@aspectlylabs/mikka@0.0.374
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reviewed credential flow uses a local broker to forward supported model requests to the selected provider, while hosted runs use a broker socket and placeholder credentials. The harness installer verifies pinned artifact integrity; the reported shell and process execution matches the package’s daemon and agent-runner purpose.
Decision evidence
public snapshot- The manifest exposes a daemon CLI and JavaScript entry points; it declares no lifecycle scripts.
- The API-key broker restricts requests to Anthropic or OpenAI API paths and sends them to the credential’s configured provider base URL.
- The hosted runner passes a placeholder credential to its CLI and routes model requests through a local broker.
- The harness installer downloads pinned artifacts and checks their SHA-512 integrity before unpacking them.
- No reviewed source showed credentials being sent to an unrelated host or unrelated install-time contact.
- The reported shell and process execution occurs in harness installation and agent-runner code, consistent with the package’s stated purpose.
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.374.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.374 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.