registry / @aspectlylabs/mikka / 0.0.301
@aspectlylabs/mikka@0.0.301
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 constrained model API broker: credentials go to the selected provider for allowed model paths, with redirects rejected. The manifest has no install hooks, and the subprocess and network use inspected here fit the package's daemon and agent purpose.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
A user runs the CLI or daemon and starts an agent run using a configured provider credential.
Impact
No unauthorized credential collection, unrelated destination, or automatic install-time action was found in the inspected source.
Mechanism
A local broker accepts only designated model API requests, adds the run credential, and forwards requests to the official provider endpoint or the run's configured HTTPS provider URL.
AI rationale
The flagged credential flow is a constrained model API broker: credentials go to the selected provider for allowed model paths, with redirects rejected. The manifest has no install hooks, and the subprocess and network use inspected here fit the package's daemon and agent purpose.
Network endpoints3
api.anthropic.comapi.openai.com/v1configured HTTPS provider URL
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 identifies Mikka as a local daemon and defines its CLI and module entry points; it declares no lifecycle scripts.
- The API-key broker uses official Anthropic and OpenAI endpoints by default and restricts requests to a small set of model API paths.
- Provider credentials are sent to the supplied HTTPS provider URL; the broker forwards the credential only to that origin and rejects redirects.
Evidence against
- The package uses subprocesses and network access as part of its agent-daemon functionality.
- Managed auto-update code exists, but its runtime path requires it to be enabled in production under systemd or launchd.
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.301.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.301 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.