@aspectlylabs/mikka@0.0.414
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged credential flow is a provider API broker: it uses the run credential's HTTPS base URL, restricts request paths, and rejects redirects. The new MCP file's shell capability is limited to explicitly invoked, host-configured verification checks; no malicious behavior was found.
Decision evidence
public snapshot- The full manifest has no install, preinstall, or postinstall lifecycle scripts.
- The API-key broker accepts an HTTPS provider URL from the run credential and checks that its protocol matches the requested provider.
- The broker forwards the API key to that configured origin, restricts requests to provider API paths, and disables redirects.
- The MCP verification tool is available only when configured for a Factory check and validates the command against host-provided settings before execution.
- The package provides a local daemon for running agents through the user's own CLIs, consistent with its declared purpose.
- The broker sends credentials to the configured model provider rather than a fixed publisher-controlled destination.
- Verification commands run through an explicit MCP tool call, not automatically during installation or import.
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.414.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.414 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.