registry / @nanonets/graft / 0.24.0
@nanonets/graft@0.24.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 13d ago · by lpm-firewall-aiThe inspected telemetry and CLI picker behavior do not establish an attack. The declared Anthropic SDK dependency has an unresolved, truncated source snapshot, so the package cannot be cleared on the available evidence.
Static reason
One or more suspicious static signals were detected.; previous stored version diff introduced dangerous source
Trigger
Installing or using the package may load its declared dependencies.
Impact
The unresolved dependency prevents confirming the package’s full behavior from source.
Mechanism
The available snapshot does not expose the unresolved dependency’s source for review; the inspected install telemetry path is gated and sends a limited event to the Nanonets collector.
AI rationale
The inspected telemetry and CLI picker behavior do not establish an attack. The declared Anthropic SDK dependency has an unresolved, truncated source snapshot, so the package cannot be cleared on the available evidence.
Evidence
package.json.lpm-dependency-evidence-3ccdd6eb-fea6-4a61-8adb-0cd0e09ef964/2/npm-linux.tgz
Network endpoints1
events.nanonets.com
Decision evidence
public snapshotAI called this Manual Review at 87.0% confidence as Unknown with medium false-positive risk.
AI review observations
- The package runs a postinstall hook that records an install event outside CI.
- Install telemetry is gated by a key, DO_NOT_TRACK, CI, and a saved disable setting; it defaults on otherwise.
- The install event is limited to a global-install flag and is sent to the configured Nanonets collector.
- The manifest declares the Anthropic SDK, but its prepared source snapshot could not be inspected.
- The unresolved CLI picker receiver formats labels for display.
Evidence against
- The inspected install telemetry source shows a gated, limited event sent to the package’s stated collector.
- The inspected CLI picker receiver maps hidden rows to labels for display; it does not establish an attack.
Behavioral surface
ChildProcessCryptoDynamicRequireEnvironmentVarsFilesystemNetworkShell
HighEntropyStringsMinifiedUrlStrings
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/shim-template.js#virtual:normalized:round1View file
24return `#!/usr/bin/env node
L25: const path = require("path");
L26: const fs = require("fs");
Medium
Dynamic Require
Package source references dynamic require/import behavior.
dist/claude/shim-template.js#virtual:normalized:round1Findings
4 High5 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/shim-template.js#virtual:normalized:round1
MediumNetwork
MediumEnvironment Vars
MediumStructural Risk Force Deep Review
LowNon Install Lifecycle Scripts
LowScripts Present
LowWeak Cryptodist/notes/learning-fields.js
LowFilesystem
Affected versions and remediation
This report applies to @nanonets/graft@0.24.0.
See all versions of @nanonets/graft for other recorded verdicts.
- Review the evidence and your use of @nanonets/graft@0.24.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.