@aspectlylabs/mikka@0.0.388
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest describes a local daemon that runs agents, and the examined credential path validates HTTPS destinations and brokers requests for a selected run. The scanner's credential and shell flags are consistent with these features; the inspected code did not establish an unrelated credential redirect or other attack.
Decision evidence
public snapshot- The manifest exposes a CLI at mikka.js and the package entry at main.js.
- Provider credentials are checked for HTTPS URLs and passed to a broker for a selected agent run.
- The broker restricts requests to expected model API paths, and provider keys are attached to requests sent to the configured provider.
- The package uses network access and handles API credentials, but the inspected flow sends them to the provider endpoint configured for the run.
- The broker runs under the daemon state directory and does not show an unrelated credential destination or an automatic install-time action.
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.388.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.388 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.