@aspectlylabs/mikka@0.0.438
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe reviewed credential flow forwards model requests through a broker to the configured HTTPS provider, and the flagged process execution runs the configured agent CLI. I found no evidence of unrelated collection or unauthorized actions.
Decision evidence
public snapshot- The manifest exposes a daemon CLI and library entry points, consistent with the package’s stated purpose of running agents through users’ CLIs.
- The CLI’s default production service is https://app.aspectlylabs.com/mikka.
- Provider credentials require an HTTPS base URL without embedded username or password.
- The API-key broker sends the credential to that configured provider URL, or the protocol’s default provider endpoint, and rejects redirects.
- The native container proxies model requests through a mounted broker socket; the flagged child process runs the configured CLI and connects its standard streams to the user’s process.
- The flagged shell and process execution support the package’s agent-running function.
- Network requests carry device or run traffic to the configured Mikka service and model provider endpoints.
- No install lifecycle scripts are declared in the package manifest.
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.438.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.438 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.