@aspectlylabs/mikka@0.0.381
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 an API-key broker for agent requests: its defaults are official provider APIs, and custom HTTPS bases are accepted for configured provider credentials. The package has no install lifecycle scripts, and the reviewed harness installer verifies downloads against pinned integrity values.
Decision evidence
public snapshot- The manifest has no lifecycle scripts and exposes the daemon CLI and JavaScript entry points.
- Model credentials are sent to the official Anthropic or OpenAI API by default; a provider URL is used only when configured as a provider credential.
- The local API-key broker restricts requests to supported API paths and rejects non-HTTPS credential destinations.
- Managed harness downloads are checked against pinned SHA-512 integrity before extraction.
- The daemon uses subprocesses and network requests as part of its advertised purpose of running agents through local CLIs.
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.381.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.381 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.