@aspectlylabs/mikka@0.0.302
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe reviewed credential flow serves the package's stated purpose of running agents through local CLIs: provider URLs are configuration inputs, HTTPS and protocol are checked, and runs require a scoped approval gate. The scanner's execution and network flags match these expected capabilities; no unrelated credential destination or automatic attack behavior was found.
Decision evidence
public snapshot- The manifest describes a local daemon that runs agents through the user's own CLIs.
- Custom provider credentials require an HTTPS URL without embedded username or password.
- The API broker uses the configured provider URL or the standard Anthropic/OpenAI endpoint and checks protocol compatibility.
- The broker sends the key with API requests to that upstream and rejects redirects.
- Starting a run requires a run-scoped tool approval gate.
- The daemon supports process execution, network requests, and credential handling as part of running AI agents.
- A user-configured compatible provider URL can receive the associated model key during agent requests.
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.302.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.302 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.