@aspectlylabs/mikka@0.0.323
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe inspected credential flow forwards run requests to the credential's configured HTTPS provider, defaulting to official Anthropic or OpenAI endpoints, and refuses redirects. The manifest has no install lifecycle scripts; the scanner's execution and credential-routing leads match the package's local agent-daemon purpose.
Decision evidence
public snapshot- The manifest defines a CLI and module entry points and has no lifecycle scripts.
- The API key broker defaults to the official Anthropic and OpenAI API hosts; custom provider URLs come from the credential configuration and must use HTTPS.
- The broker sends keys only to the configured upstream, restricts accepted API paths, and refuses redirects.
- Provider credentials are checked for HTTPS endpoints before being passed to the matching agent CLI.
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.323.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.323 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.