@aspectlylabs/mikka@0.0.290
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential flow forwards a run's configured API key to its configured provider origin, while the journal strips that key before persistence. The new driver is a constrained, permission-gated daemon capability and does not show unrelated execution or collection.
Decision evidence
public snapshot- The manifest describes a local daemon that runs agents through the user's own CLIs.
- Run credentials support either a plain API key or a provider credential with an explicitly supplied base URL.
- Provider URLs must use HTTPS and cannot include embedded credentials, a query, or a fragment.
- The API broker sends the key to the credential's configured origin and rejects redirects.
- The run journal removes model credentials before persisting entries.
- Computer-driver actions are restricted to daemon-approved calls and require the run's computer-use permission.
- The daemon makes network requests to model-provider APIs during runs, which is consistent with its stated purpose.
- The package can launch local agents and a computer driver, but the reviewed code scopes these capabilities to configured runs and approved actions.
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.290.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.290 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.