@aspectlylabs/mikka@0.0.417
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe manifest has no install hooks, and the reviewed credential broker forwards run requests to the specified provider's API routes, defaulting to Anthropic or OpenAI. The source reviewed does not support the scanner's claim of an automatic redirect to an unofficial gateway or persistent credential redirection.
Decision evidence
public snapshot- The manifest has no lifecycle scripts; it exposes a daemon CLI and JavaScript entry points.
- The API-key broker defaults to Anthropic and OpenAI API hosts and accepts only the providers' specified API routes.
- The broker is created for an assignment's model credential; custom provider URLs are passed through as that provider's base URL.
- GitHub credentials are described as run-scoped credentials fetched with a run token and cached locally with restrictive permissions.
- The daemon runs agent CLIs and forwards user prompts and run data as part of its stated purpose.
- The broker can send requests to a custom HTTPS provider URL supplied in the run credential.
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.417.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.417 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.