@nanonets/graft@0.20.0
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 1mo ago · by lpm-firewall-aiThe package has a guarded but meaningful capability to change AI-agent configuration through its explicit init workflow. Static inspection found no confirmed install-time control-surface hijack, credential theft, or code execution from checked-out repositories.
Decision evidence
public snapshot- The init command stops without a selected agent, so agent wiring follows an explicit command choice.
- When Claude is selected, init writes project agent settings, executable helper shims, and a skill.
- Init also retracts configuration for unselected agent hosts, so it can alter existing agent integration state.
- The context writer limits its project change to a rooted gitignore entry for its cache.
- The checkout helper disables repository Git hooks and does not execute fetched code.
- The browser handoff rejects callbacks whose random state does not match.
Source & flagged code
5 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.
scripts/postinstall.mjsView on unpkg · L27Findings
Affected versions and remediation
This report applies to @nanonets/graft@0.20.0.
See all versions of @nanonets/graft for other recorded verdicts.
- Review the evidence and your use of @nanonets/graft@0.20.0 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.