@aspectlylabs/mikka@0.0.348
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe flagged credential flow is a provider proxy used for an assigned agent run. Its destination comes from the provider credential, is restricted to HTTPS, and redirects are rejected; the reviewed source showed no unrelated credential exfiltration or malicious automatic action.
Decision evidence
public snapshot- Provider URLs must use HTTPS and cannot include embedded credentials, query strings, or fragments.
- The API-key broker uses the credential’s configured origin, or Anthropic/OpenAI defaults, and rejects redirects.
- The broker flow starts as part of an agent run that has an assigned model credential.
- The manifest describes a local daemon for running agents through the user’s own CLIs and declares no lifecycle scripts.
- Hosted child processes reject unexpected credential-bearing environment variables.
- The package runs agents and uses network requests and subprocesses as part of its stated purpose.
- The flagged credential and command paths have ordinary run, provider, or daemon-management contexts; no unrelated credential collection or destination was identified.
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.348.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.348 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.