@aspectlylabs/mikka@0.0.371
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe routing hints are consistent with a provider credential broker: credentials are attached to requests sent to the configured HTTPS provider endpoint, with official provider defaults and redirect rejection. The manifest has no lifecycle scripts, and the reviewed source does not establish an unrelated credential destination or harmful automatic behavior.
Decision evidence
public snapshot- The manifest defines a CLI entry and module exports, with no lifecycle scripts shown.
- The API key broker uses the supplied credential and protocol, then forwards requests to the credential's configured HTTPS base URL or the official Anthropic/OpenAI default.
- The broker adds the credential to the corresponding provider authorization header and rejects redirects.
- The custom provider URL is validated as HTTPS and cannot include embedded credentials.
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.371.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.371 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.