registry / @aspectlylabs/mikka / 0.0.272
@aspectlylabs/mikka@0.0.272
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 broker for model requests: it validates HTTPS provider configuration and forwards credentials to that configured provider. The added computer driver is invoked for explicit computer actions with a pre-action callback; the manifest has no install lifecycle scripts.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Provider requests and computer actions occur when an agent run invokes them.
Impact
No unauthorized credential collection, unrelated data transfer, or unrequested account action was identified.
Mechanism
The API-key broker forwards requests to the configured HTTPS provider endpoint; computer actions use a local driver and an approval callback.
AI rationale
The flagged credential flow is a broker for model requests: it validates HTTPS provider configuration and forwards credentials to that configured provider. The added computer driver is invoked for explicit computer actions with a pre-action callback; the manifest has no install lifecycle scripts.
Network endpoints3
api.anthropic.comapi.openai.comuser-configured HTTPS provider host
Decision evidence
public snapshotAI called this Clean at 91.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest describes a local daemon that runs agents through the user's own CLIs and exposes its CLI and module entry points.
- Provider credentials are accepted only with an HTTPS base URL; the broker uses that provider URL or the standard Anthropic/OpenAI endpoint.
- The broker sends the credential with POST requests to the configured origin and rejects redirects.
- The native runner proxies requests through a local broker socket.
- Desktop driver operations run after the beforeAction callback and a liveness check.
Evidence against
- The manifest contains no lifecycle scripts, and the reviewed credential flow is tied to configured model-provider requests.
- The desktop driver exposes purpose-specific computer actions rather than arbitrary shell commands.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStrings
Source & flagged code
6 flaggedgithub-credentials.mjsView file
4import { randomUUID } from 'node:crypto'
L5: import { spawn } from 'node:child_process'
L6: import { pathToFileURL } from 'node:url'
High
Child Process
Package source references child process execution.
github-credentials.mjsView on unpkg · L4mikka.jsView file
4562ai: "7.0.142",
L4563: execa: "10.1.1",
L4564: pino: "10.4.0",
High
6339assertSafeId("run id", runId);
L6340: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6341: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6350: }
L6351: async function pinnedGit(repoPath, worktree, env = process.env) {
L6352: const gitDir = await worktreeGitDir(repoPath, worktree);
L6353: const workTree = realpathSync4(worktree);
L6354: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6355: cwd: workTree,
Findings
1 Critical5 High2 Medium4 Low
CriticalPrevious Version Dangerous Deltacomputer/driver.mjs
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
Affected versions and remediation
This report applies to @aspectlylabs/mikka@0.0.272.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.272 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.