@aspectlylabs/mikka@0.0.418
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe routing hints identify credential handling and process execution, but the inspected flows serve the package’s agent runner: provider credentials are forwarded only to the configured HTTPS origin or standard provider endpoint, and GitHub credentials are scoped to user-authorized run operations. No install hook or unrelated credential collector was found.
Decision evidence
public snapshot- The manifest exposes a local daemon and CLI through its main entry points and declares no lifecycle scripts.
- The API-key broker accepts the supplied credential’s HTTPS base URL, or the standard Anthropic/OpenAI endpoint, and rejects credentials containing invalid values.
- The broker forwards requests to that selected origin with the provider credential and disables redirects.
- The GitHub credential helper describes a run-scoped credential cache for GitHub operations the user authorized.
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.418.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.418 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.