registry / @aspectlylabs/mikka / 0.0.303
@aspectlylabs/mikka@0.0.303
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hooks, and the flagged credential and process flows fit the package’s local agent daemon purpose. The reviewed model-key broker targets configured providers or official Anthropic and OpenAI API endpoints, with no evidence of a fixed unofficial gateway or unrelated data collection.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
No malicious automatic trigger was found; desktop actions run through the daemon’s driver interface.
Impact
No unauthorized credential disclosure or unrelated execution was identified.
Mechanism
Model API credentials are forwarded to the configured provider or the official Anthropic and OpenAI API origins. The desktop adapter invokes a verified driver for requested actions.
AI rationale
The manifest has no install hooks, and the flagged credential and process flows fit the package’s local agent daemon purpose. The reviewed model-key broker targets configured providers or official Anthropic and OpenAI API endpoints, with no evidence of a fixed unofficial gateway or unrelated data collection.
Network endpoints2
api.anthropic.comapi.openai.com
Decision evidence
public snapshotAI called this Clean at 92.0% confidence as Benign with low false-positive risk.
Evidence for AI clean decision
- The manifest has no install lifecycle scripts and exposes the daemon and CLI entry points.
- The API key broker uses a configured provider URL or defaults to api.anthropic.com and api.openai.com; it forwards requests to that selected origin.
- The desktop driver is an explicit daemon action and its source states it does not expose shell, host credentials, or arbitrary tool names.
Evidence against
- The package runs subprocesses and makes network requests as part of its local daemon and agent functionality.
- The scanner’s credential redirection and command execution leads did not reveal a fixed unofficial credential destination or unrelated automatic execution.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
CopyleftLicense
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.303.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.303 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.