registry / @nanonets/graft / 0.27.0
@nanonets/graft@0.27.0
⚠ Under reviewBuild 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 8d ago · by lpm-firewall-aiThe postinstall telemetry is package-aligned and sends a narrowly scoped install event behind telemetry gates. I cannot clear the package because the shipped native binaries have unresolved behavior in the available analysis.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Loading a native grammar binary through the package’s parser functionality.
Impact
The native binaries’ effects cannot be ruled out from the available evidence.
Mechanism
The available analysis leaves native call targets uninspected, preventing a determination of their full behavior.
AI rationale
The postinstall telemetry is package-aligned and sends a narrowly scoped install event behind telemetry gates. I cannot clear the package because the shipped native binaries have unresolved behavior in the available analysis.
Evidence
.lpm-inspection-zPzvyH/3-cebd63f7c915.txt
Network endpoints1
events.nanonets.com
Decision evidence
public snapshotAI called this Manual Review at 58.0% confidence as Unknown with medium false-positive risk.
AI review observations
- package.json runs scripts/postinstall.mjs after installation.
- The install hook queues an install event and launches a detached telemetry flush.
- Telemetry sends to the package’s events.nanonets.com endpoint; the event is limited to a global-install flag.
- The telemetry gate is open by default unless a disable setting or another gate closes it.
- The inspected native analysis reports uninspected call targets, so native behavior remains unresolved.
Evidence against
- The postinstall hook skips telemetry in CI, and telemetry can be disabled with DO_NOT_TRACK or a saved setting.
- The install event’s declared field is limited to the global-install flag.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
Source & flagged code
8 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
4 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
HighPrevious Version Dangerous Deltadist/cli.js
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 Crypto
Affected versions and remediation
This report applies to @nanonets/graft@0.27.0.
See all versions of @nanonets/graft for other recorded verdicts.
- Review the evidence and your use of @nanonets/graft@0.27.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.