registry / @aspectlylabs/mikka / 0.0.361
@aspectlylabs/mikka@0.0.361
Local Mikka daemon: runs agents through the user's own CLIs
AI Security Review
scanned 2d ago · by lpm-firewall-aiThe manifest has no install hooks, and the credential flow inspected uses the configured provider with official Anthropic or OpenAI endpoints as defaults. The shell and network findings align with the package’s stated purpose of running agents through the user’s CLIs.
Static reason
One or more suspicious static signals were detected.
Trigger
CLI use and an agent run.
Impact
No malicious impact identified; model credentials are used for the selected provider requests.
Mechanism
The broker forwards model requests to the configured provider, using official Anthropic or OpenAI API hosts by default and rejecting redirects.
AI rationale
The manifest has no install hooks, and the credential flow inspected uses the configured provider with official Anthropic or OpenAI endpoints as defaults. The shell and network findings align with the package’s stated purpose of running agents through the user’s CLIs.
Network endpoints2
api.anthropic.comapi.openai.com/v1
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 has no lifecycle scripts; it exposes a CLI and library entry points.
- The API-key broker defaults to Anthropic’s and OpenAI’s official API hosts.
- Credentials are used by the broker for requests to the selected provider, with redirects disabled.
- The broker starts as part of an agent run and the request path is restricted to supported model API routes.
Evidence against
- The daemon executes agent CLIs, which matches the package’s stated purpose.
- A provider credential can specify a custom HTTPS base URL, so the user’s selected provider receives that credential.
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
4625ai: "7.0.142",
L4626: execa: "10.1.1",
L4627: pino: "10.4.0",
High
6446assertSafeId("run id", runId);
L6447: const common = resolve4(await worktreeGitDir(repoPath, worktree), "..", "..");
L6448: if (basename(common) !== ".git") throw new Error(`${repoPath} is not a standard clone`);
...
L6457: }
L6458: async function pinnedGit(repoPath, worktree, env = process.env) {
L6459: const gitDir = await worktreeGitDir(repoPath, worktree);
L6460: const workTree = realpathSync4(worktree);
L6461: return (args, extra, options) => execa3("git", [...SAFE_GIT, ...args], {
L6462: 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.361.
See all versions of @aspectlylabs/mikka for other recorded verdicts.
- Review the evidence and your use of @aspectlylabs/mikka@0.0.361 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.