@aspectlylabs/mikka@0.0.300
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe scanner findings are consistent with normal package behavior: credential routing is constrained to official defaults or an explicitly configured HTTPS provider, and the optional driver supports computer actions. The reviewed manifest has no install lifecycle scripts, and the inspected sources show no unrelated credential exfiltration.
Decision evidence
public snapshot- The manifest exposes the CLI and library entrypoints and has no install lifecycle scripts.
- Built-in API key broker destinations are the official Anthropic and OpenAI API endpoints.
- A configured provider URL must use HTTPS and cannot include embedded credentials, a query, or a fragment.
- The run mailbox accepts only an assigned URL matching the configured server endpoint and passing its trusted endpoint check.
- The computer driver is optional and is invoked by an exported function after driver detection; its execution is tied to computer 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.300.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.300 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.