dokkimi
CLI for isolated Docker environments for microservice testing
This report shows the evidence for dokkimi@0.5.10. 4 of 5 known versions are blocked or flagged. See all versions.
AI Security Review
scanned 1mo ago · by lpm-firewall-aiThis is a concrete automatic postinstall chain that writes foreign global AI-agent settings and prompts. It meets the install-control-surface blocking policy.
Decision evidence
public snapshot- The package automatically runs a postinstall script.
- That script imports and invokes LLM-context registration during installation.
- The registration code writes a Dokkimi MCP command into global Claude Code and Cursor configuration files.
- It also writes instruction files into Claude Code, Cursor, and GitHub Copilot locations without a user command or consent.
- No network endpoint or credential-exfiltration sink was established in the inspected installation path.
Source & flagged code
19 flagged · loading sourcePackage defines install-time lifecycle scripts.
package.jsonView on unpkgInstall-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgPackage source references child process execution.
shared/platform/dist/platform-unix.jsView on unpkg · L3Findings
Affected versions and remediation
This report applies to dokkimi@0.5.10.
The versions list below shows the verdict for each recorded version.
- Avoid installing dokkimi@0.5.10. Remove it from direct dependencies and check your lockfile for transitive copies.
- Choose an independently verified alternative or release. This report does not establish that other versions are safe.
- If this version ran, investigate the affected machine and build environment. Rotate credentials it could access and rebuild from a trusted environment.
Evidence last updated: .
Think this verdict is wrong? Dispute it on GitHub or read how reports are produced.