registry / @aspectlylabs/mikka / 0.0.419
@aspectlylabs/mikka@0.0.419
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe flagged credential flow is a local broker for assigned agent runs: ordinary API keys use official provider endpoints, and provider credentials route to their configured origin. I found no evidence of an unsolicited redirect or credential persistence.
Static reason
One or more suspicious static signals were detected.
Trigger
A run starts with an assigned model credential.
Impact
No unauthorized credential redirection, collection, or persistence was identified in the reviewed paths.
Mechanism
A local broker forwards supported API requests to the credential's provider origin; ordinary API-key credentials use official Anthropic or OpenAI endpoints.
AI rationale
The flagged credential flow is a local broker for assigned agent runs: ordinary API keys use official provider endpoints, and provider credentials route to their configured origin. I found no evidence of an unsolicited redirect or credential persistence.
Network endpoints2
api.anthropic.comapi.openai.com
Decision evidence
public snapshotAI called this Clean at 94.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 has no lifecycle scripts.
- The API-key broker defaults to the official Anthropic and OpenAI API endpoints and only accepts specific API paths.
- The broker sends credentials to the origin derived from the run credential; its use is tied to an assigned model credential.
- The package exposes a CLI and daemon modules, consistent with its stated purpose.
Evidence against
- The package uses subprocesses, filesystem access, and network requests as part of running agent CLIs and brokering their API requests.
Behavioral surface
ChildProcessCryptoEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsUrlStrings
CopyleftLicense
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
4637ai: "7.0.142",
L4638: execa: "10.1.1",
L4639: pino: "10.4.0",
High
6566assertSafeId("run id", runId);
L6567: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6568: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6577: }
L6578: async function pinnedGit(repoPath, worktree, env = process.env) {
L6579: const gitDir = await worktreeGitDir(repoPath, worktree);
L6580: const workTree = realpathSync4(worktree);
L6581: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6582: 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.419.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.419 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.