graft@0.30.1
CAUTION· startup onlyPublisher claims: "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." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
What this means for the label: Caution here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso trailhq.com, acme.internal — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it under the guard. Startup only; authenticated tool behavior not tested. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 0.29.0
vet-skills diff graft 0.29.0 0.30.1In the sandbox, this version reached for nothing 0.29.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-18 and scored it 63/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Privileged sudo command; Privileged sudo command; Privileged sudo command. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 31 s · 3 scenarios · 0 deviationsStatic findings
* system package): an npm prefix in the home folder, set once. Not sudo: a sudoFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell./** True when the running module lives under an npx cache dir (e.g.Fix: Pin versions and sources; vendor anything fetched at install time.`npm needs sudo to write to ${path}.`,Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* block it (`clearNpmLeftover`) and turning EACCES into the no-sudo fix, thenFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* `[email protected]:NanoNets/Graft.git`, `https://user:[email protected]/NanoNets/Graft`Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.* block it (`clearNpmLeftover`) and turning EACCES into the no-sudo fix, thenFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* system package): an npm prefix in the home folder, set once. Not sudo: a sudoFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.env: opts.session ? { ...env, CLAUDE_CODE_SESSION_ID: opts.session } : env,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><b>Method</b></summary> Two clones of PocketBase at the same commit: one wired with `graft init`, one untouched and verified to have no graft map in itFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.* false — `graft upgrade` would then run `npm install -g` on top of an npx run.Fix: Pin versions and sources; vendor anything fetched at install time.console.log(`An earlier send stopped with ${left} of ${earlier.manifest.items.length} items left (${homePath(earlier.dir)}).`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.* false — `graft upgrade` would then run `npm install -g` on top of an npx run.Fix: Pin versions and sources; vendor anything fetched at install time.| You write and update CLAUDE.md by hand | Learnings are saved from your conversations, in files you can read |Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct./** Runs `npm install -g @nanonets/graft@latest`, clearing npm leftovers thatFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed./** Runs `npm install -g @nanonets/graft@latest`, clearing npm leftovers thatFix: Pin the exact version (`[email protected]`, `==1.2.3`) so every install gets the bytes that were reviewed.// Codex, Hermes and Antigravity all write AGENTS.md: list each write once.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.console.log(` meaning: ${m.computed} computed, ${m.cached} cached, ${m.stale} stale, ${m.pending} pending`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.return (`running via npx: npx already fetches the latest ${brand()} on every run.\n` +Fix: Pin versions and sources; vendor anything fetched at install time.…:-]+ ){0,3}?`; const RUNNER = String.raw `(?:npm|pnpm|yarn|bun)(?: run)? test\b|npx (?:vitest|jest|playwright test)\b|go test\b|cargo test\b|make test\w*|python3? -m pytest\b|pytest\b|bats\…Fix: Pin versions and sources; vendor anything fetched at install time./** Env kill switch, mirroring `GRAFT_NO_REFRESH` in ./refresh.ts. */Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…aph yet \u2014 run <code>graft graph</code> to generate <span class="mono">graph.json</span>.'));else{let i=J();!i||i.nodes.length===0?lt(i?.meta.emptyNote?Ht(i.meta.emptyNote):e==="code"?'No code graph yet \u2014 run <code>graft graph</co…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.console.log(`· send one: ${cmd("graft share-session")} <number>`);Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why./** True when `npm install -g` actually ran (false for the npx no-op path). */Fix: Pin versions and sources; vendor anything fetched at install time./** True when the running module lives under an npx cache dir (e.g.Fix: Pin versions and sources; vendor anything fetched at install time.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for @nanonets/graft@0.30.1 as of 26 min ago. This is the package itself, not its dependencies.
What would make this Verified
17 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim nanonets: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- Privileged sudo command≈ +4 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
- URL with embedded credentials≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Unpinned dependencies≈ +3 on the totalPin exact versions (and ideally hashes) in package.json, requirements or the install script so the bundle cannot change under you.