@nanonets/graft@0.12.1
Build a repo's context graph as a folder of linked markdown files: a local, regenerable cache that every query keeps in sync with your code.
AI Security Review
scanned 2mo ago · by lpm-firewall-aiNo concrete malicious install-time behavior or exfiltration chain was found. The explicit global AI-agent hook/MCP installation is a meaningful lifecycle risk that warrants a warning under policy.
Decision evidence
public snapshot- Explicit `graft init` wires AI-agent instruction, MCP, hook, and statusline integration.
- When Codex is detected, init targets the global `~/.codex/config.toml` MCP configuration.
- Init installs global Codex lifecycle hooks that run a Graft shim on SessionStart, prompt submission, edits, and Stop.
- Runtime telemetry posts queued analytics batches to Nanonets' PostHog endpoint.
- `postinstall` only prints an opt-in init nudge; it performs no configuration write.
- Agent wiring is reachable through the explicit `init` command and offers dry-run and `--no-global` safeguards.
- No install-time payload execution, credential harvesting, destructive action, or remote code loading was found.
Source & flagged code
4 flaggedPackage 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 dynamic require/import behavior.
dist/claude/shim-template.jsView on unpkg · L22Findings
Affected versions and remediation
This report applies to @nanonets/graft@0.12.1.
See all versions of @nanonets/graft for other recorded verdicts.
- Review the evidence and your use of @nanonets/graft@0.12.1 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.