@aspectlylabs/mikka@0.0.279
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe suspicious scanner leads resolve to normal daemon behavior: agent credentials go to the selected provider through a path-restricted broker, and mailbox credentials are bound to the assigned server endpoint. The manifest has no lifecycle scripts, and the reviewed source does not show a fixed unofficial gateway or unrelated collection.
Decision evidence
public snapshot- The manifest exposes a daemon CLI and API entry points; it has no lifecycle scripts.
- The API key broker uses the official Anthropic and OpenAI endpoints by default, or an HTTPS provider URL configured for the run.
- The broker accepts only the API paths for the selected provider protocol.
- The configured key is sent to that provider endpoint, and redirects are rejected.
- Run mailbox access is disabled unless assigned; when enabled, its URL must match the run’s server endpoint.
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.279.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.279 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.