registry / @aspectlylabs/mikka / 0.0.425
@aspectlylabs/mikka@0.0.425
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 22h ago · by lpm-firewall-aiThe flagged credential flow is a model-provider proxy: it validates HTTPS provider configuration and routes supported requests to that configured origin. The package manifest shows no install lifecycle scripts, and the reviewed source does not show credentials being redirected to a fixed unrelated gateway.
Static reason
One or more suspicious static signals were detected.
Trigger
A run starts with a model credential and provider configuration.
Impact
The provider receives the requests needed to run the user-configured model.
Mechanism
The daemon brokers requests to the configured HTTPS origin, using the provider credential for supported API calls and rejecting redirects.
AI rationale
The flagged credential flow is a model-provider proxy: it validates HTTPS provider configuration and routes supported requests to that configured origin. The package manifest shows no install lifecycle scripts, and the reviewed source does not show credentials being redirected to a fixed unrelated gateway.
Evidence
host.root/api-key-broker-*/broker.sock
Network endpoints3
api.anthropic.comapi.openai.comConfigured HTTPS provider origin
Decision evidence
public snapshotAI called this Clean at 96.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest exposes a daemon CLI and module entry points; it declares no install lifecycle scripts.
- Configured model-provider URLs must use HTTPS and cannot include embedded credentials, query strings, or fragments.
- The API-key broker forwards model requests to the configured provider origin and rejects redirects.
- Run credentials are passed in memory to the run’s CLI adapter.
Evidence against
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
CopyleftLicense
Source & flagged code
6 flaggedgithub-credentials.mjsView file
7import { randomUUID } from 'node:crypto'
L8: import { spawn } from 'node:child_process'
L9: import { pathToFileURL } from 'node:url'
High
Child Process
Package source references child process execution.
github-credentials.mjsView on unpkg · L7mikka.jsView file
4637ai: "7.0.142",
L4638: execa: "10.1.1",
L4639: pino: "10.4.0",
High
6573assertSafeId("run id", runId);
L6574: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6575: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6584: }
L6585: async function pinnedGit(repoPath, worktree, env = process.env) {
L6586: const gitDir = await worktreeGitDir(repoPath, worktree);
L6587: const workTree = realpathSync4(worktree);
L6588: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6589: cwd: workTree,
Findings
5 High2 Medium5 Low
HighChild Processgithub-credentials.mjs
HighShellmikka.js
HighSame File Env Network Executionmikka.js
HighCredential Redirect Persistencemain.js
HighCommand Output Exfiltrationagents/native-container.mjs
MediumNetwork
MediumEnvironment Vars
LowFilesystem
LowHigh Entropy Strings
LowUrl Strings
LowCopyleft License
LowSuspicious Lifecycle Evidencepackage.json
Affected versions and remediation
This report applies to @aspectlylabs/mikka@0.0.425.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.425 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.