registry / @aspectlylabs/mikka / 0.0.440
@aspectlylabs/mikka@0.0.440
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 6h ago · by lpm-firewall-aiThe flagged process execution and credential references fit a local daemon that runs agents through user CLIs. The inspected source validates provider URLs and filters secret environment variables; it does not show an automatic credential redirect or unrelated collection.
Static reason
One or more suspicious static signals were detected.
Trigger
The daemon runs when explicitly started, and agent execution follows a run assignment.
Impact
The reviewed source does not show credentials being collected or sent to an unrelated host, or another harmful automatic action.
Mechanism
It passes an assigned model credential to the selected agent CLI and filters secret-like environment variables from the child environment.
AI rationale
The flagged process execution and credential references fit a local daemon that runs agents through user CLIs. The inspected source validates provider URLs and filters secret environment variables; it does not show an automatic credential redirect or unrelated collection.
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 daemon CLI and JavaScript entry points, with no lifecycle scripts declared.
- Run model credentials are accepted only as API keys or provider credentials; custom provider URLs must use HTTPS and omit embedded credentials, query strings, and fragments.
- A run receives the model credential provided in its assignment, and the daemon passes it to the agent run; this matches the package’s stated purpose of running agents through the user’s own CLIs.
- The child environment builder excludes known provider keys, cloud credentials, GitHub and npm tokens, and other secret-like environment variables.
Evidence against
- Agent runs can execute local CLIs and make network requests as part of the daemon’s stated purpose.
- GitHub credentials may be fetched for a run from the endpoint supplied in that run’s assignment.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
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
4751ai: "7.0.142",
L4752: execa: "10.1.1",
L4753: pino: "10.4.0",
High
6760assertSafeId("run id", runId);
L6761: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6762: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6771: }
L6772: async function pinnedGit(repoPath, worktree, env = process.env) {
L6773: const gitDir = await worktreeGitDir(repoPath, worktree);
L6774: const workTree = realpathSync4(worktree);
L6775: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6776: 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.440.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.440 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.