registry / @aspectlylabs/mikka / 0.0.382
@aspectlylabs/mikka@0.0.382
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 1d ago · by lpm-firewall-aiThe scanner leads resolve to ordinary daemon, provider, and hosted-broker behavior: provider URLs are standard defaults or supplied configuration, and the broker path uses a placeholder key with endpoint validation. The manifest has no install lifecycle hooks.
Static reason
One or more suspicious static signals were detected.
Trigger
The CLI or exported modules are used by the application; provider requests occur when a run is started.
Impact
No malicious credential redirection, unrelated collection, or other attack behavior was established.
Mechanism
Provider requests use standard provider defaults or a supplied provider base URL. The hosted broker uses a placeholder credential and validates its endpoint against the configured host.
AI rationale
The scanner leads resolve to ordinary daemon, provider, and hosted-broker behavior: provider URLs are standard defaults or supplied configuration, and the broker path uses a placeholder key with endpoint validation. The manifest has no install lifecycle hooks.
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 describes a local daemon and declares no lifecycle scripts; it exposes a CLI and JavaScript entry points.
- Normal provider defaults are api.anthropic.com and api.openai.com; provider credentials may use an explicitly supplied base URL.
- The hosted broker path uses a placeholder credential instead of forwarding a provider API key.
- The broker request checks that its endpoint matches the configured host endpoint and disables redirects.
Evidence against
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
4632ai: "7.0.142",
L4633: execa: "10.1.1",
L4634: pino: "10.4.0",
High
6551assertSafeId("run id", runId);
L6552: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6553: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6562: }
L6563: async function pinnedGit(repoPath, worktree, env = process.env) {
L6564: const gitDir = await worktreeGitDir(repoPath, worktree);
L6565: const workTree = realpathSync4(worktree);
L6566: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6567: 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.382.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.382 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.