registry / @nanonets/graft / 0.25.0
@nanonets/graft@0.25.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 12d ago · by lpm-firewall-aiThe default-on install event creates a privacy exposure before telemetry preferences are configured, so a warning is appropriate. The first-party destination, limited event fields, and available opt-out gates do not establish malicious behavior.
Static reason
One or more suspicious static signals were detected.
Trigger
Installing the package through npm when its telemetry gates are open.
Impact
The publisher receives a persistent random installation identifier and limited platform and runtime details before the user has configured telemetry preferences.
Mechanism
The hook records an installation event, then launches a detached process to flush the queued event to the package's Nanonets analytics host.
AI rationale
The default-on install event creates a privacy exposure before telemetry preferences are configured, so a warning is appropriate. The first-party destination, limited event fields, and available opt-out gates do not establish malicious behavior.
Evidence
package.jsonscripts/postinstall.mjsdist/telemetry/track.jsdist/telemetry/identity.jsdist/telemetry/contract.jsdist/telemetry/key.jsdist/telemetry/send.jsdist/telemetry/gate.js~/.graft/telemetry.json~/.graft/telemetry-queue.ndjson
Network endpoints1
events.nanonets.com
Decision evidence
public snapshotAI called this Suspicious at 82.0% confidence as Dangerous Capability with medium false-positive risk.
Evidence for warning
- The package runs a postinstall hook that records an installation event and starts a detached telemetry flush.
- The install event is recorded once per machine per version and includes a persistent random installation identifier plus platform and runtime details.
- The event is sent to the package's configured Nanonets analytics host; telemetry is on by default unless a gate disables it.
- Claude setup writes configuration and helper files when the user runs the init command; this does not establish an install-time agent configuration attack.
Evidence against
- The install event's allowed property is limited to whether installation was global, in addition to common version, platform, runtime, and host-category fields.
- The telemetry code honors CI detection, a standard do-not-track setting, and a saved disable preference.
- The analytics recipient is the package's first-party Nanonets host, and the inspected setup is activated by the init command.
Behavioral surface
ChildProcessCryptoDynamicRequire
Source & flagged code
7 flaggedpackage.jsonView file
•scripts.postinstall = node scripts/postinstall.mjs
High
Install Time Lifecycle Scripts
Package defines install-time lifecycle scripts.
package.jsonView on unpkg•scripts.postinstall = node scripts/postinstall.mjs
Medium
Ambiguous Install Lifecycle Script
Install-time lifecycle script is not statically allowlisted and needs review.
package.jsonView on unpkgdist/claude/pre-bash.jsView file
87async function nodeFs() {
L88: return typeof process.getBuiltinModule === 'function' ? process.getBuiltinModule('node:fs') : await import('node:fs');
L89: }
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/claude/pre-bash.jsView on unpkg · L87Findings
3 High6 Medium6 Low
HighInstall Time Lifecycle Scriptspackage.json
HighTrigger Reachable External Ai Agent Control Surface Mutationdist/claude/init.js
HighSemantic Analysis Limiteddist/app/checkout.js#virtual:normalized:round1
MediumAmbiguous Install Lifecycle Scriptpackage.json
MediumDynamic Requiredist/claude/pre-bash.js
MediumNetwork
MediumEnvironment Vars
MediumShips Native Binarydist/vendor/tree-sitter-swift/prebuilds/win32-arm64/tree-sitter-swift.node
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptodist/init/candidates.js
LowFilesystem
Affected versions and remediation
This report applies to @nanonets/graft@0.25.0.
See all versions of @nanonets/graft for other recorded verdicts.
- Review the evidence and your use of @nanonets/graft@0.25.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.