registry / @aspectlylabs/mikka / 0.0.282
@aspectlylabs/mikka@0.0.282
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe credential flow supports the package’s agent-running purpose and directs run keys to the configured provider or official API endpoints. The static scanner’s redirect concern was not confirmed in the source reviewed.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A run using an API-key credential starts the agent and makes supported API requests.
Impact
No unauthorized credential disclosure or other attack impact was identified.
Mechanism
The broker uses the credential's HTTPS provider URL or the official Anthropic/OpenAI API base, restricts request paths, and rejects redirects.
AI rationale
The credential flow supports the package’s agent-running purpose and directs run keys to the configured provider or official API endpoints. The static scanner’s redirect concern was not confirmed in the source reviewed.
Network endpoints2
api.anthropic.comapi.openai.com
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 exposes a `mikka` command and module entry points; no install lifecycle script is declared.
- The run credential accepts an HTTPS provider URL, and the broker validates the configured URL or uses the official Anthropic/OpenAI API base.
- The broker forwards the key only to the configured origin and API path, and disables redirects.
Evidence against
- The package uses process execution, filesystem access, and network requests for its local agent daemon functionality.
- The added computer driver detects an installed, version-pinned `cua-driver`; its presence alone does not show harmful behavior.
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.282.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.282 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.