@aspectlylabs/mikka@0.0.281
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential flow is a constrained API broker that uses official provider endpoints by default and requires HTTPS for configured provider URLs. The login path targets the selected Mikka server, with no evidence of an unrelated fixed credential destination.
Decision evidence
public snapshot- The package describes itself as a local daemon that runs agents through the user’s own CLIs.
- API-key broker defaults to the official Anthropic and OpenAI API hosts.
- The broker requires HTTPS and uses the configured provider URL when the credential specifies one.
- The broker forwards the key to that configured upstream for supported API requests.
- The CLI defaults to the package’s service and supports an explicit server URL for login and daemon use.
- The scanner’s execution and network flags align with the package’s stated daemon and agent-running purpose.
- The reviewed login flow sends device-login requests to its selected server; it does not show credentials being redirected to an unrelated fixed host.
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.281.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.281 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.