@aspectlylabs/mikka@0.0.389
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and the reviewed credential flow sends keys only to the configured HTTPS model provider, using official Anthropic or OpenAI endpoints by default. The scanner’s credential and shell findings are consistent with documented daemon and agent-runner behavior, not evidence of an unauthorized redirect.
Decision evidence
public snapshot- The manifest defines a daemon CLI and JavaScript exports, with no lifecycle scripts.
- API keys for custom providers are sent to the HTTPS base URL specified in the provider credential; otherwise the broker uses the official Anthropic or OpenAI API URL.
- The API-key broker restricts forwarded requests to specific API paths and rejects redirects.
- The documented default daemon server is app.aspectlylabs.com/mikka, matching the CLI's configured production server.
- The package executes child processes and performs network operations as part of its local daemon and agent-runner functionality.
- Custom provider credentials are deliberately forwarded to the provider URL supplied in the credential.
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.389.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.389 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.