Skip to main content
SkillTotal

Is langchain (npm) safe?

No malicious indicators - review capabilities before installing
Notable — review in context (a capability is not a malicious indicator):
  • Node.js filesystem read
  • Node.js filesystem write/delete

What to do: Nothing here argues against installing it. Grant the capabilities it lists only if you expect the tool to need them.

langchain (npm) is an npm package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators. It can: filesystem read and filesystem write — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

langchain 1.6.6

npm package · npm:langchain
LOW
0
/ 100 risk score
Snapshot · scanned Nov 13, 2026 · langchain@1.6.6 · engine 1.1.0 / ruleset 100

Get notified when this component changes

Change alerts aren't live yet. Leave your email and we'll let you know when they launch. We use it only for this and delete it on request.

Automated static-analysis result. It can contain false positives and false negatives, and is not a claim about the intent of langchain (npm)'s authors. Report a false positive.

Capabilities — what this component can do (not a risk score):
filesystem readfilesystem write

Behavioral traits

How this component maps to the CSA agentic threat model. Descriptive — it never affects the risk score.

Filesystem reach
Tool Execution Context

Findings (2)

CapabilityNode.js filesystem readnot scored · severity mediumST-FS-NODE-READ

The component reads files from disk.

const fileContent = await node_fs_promises.readFile(this.getFullPath(key));
const fileContent = await fs.readFile(this.getFullPath(key));

Why it matters: Usually legitimate, but worth confirming it can't be steered into reading sensitive files.

Fix: Confirm which files are read and that paths cannot be influenced by untrusted input to reach sensitive locations.

CapabilityNode.js filesystem write/deletenot scored · severity mediumST-FS-NODE-WRITE

The component writes or deletes files on disk.

await node_fs_promises.unlink(this.getFullPath(key));
await Promise.all(entries.filter((file) => file.endsWith(".tmp")).map((tempFile) => node_fs_promises.unlink(node_path.join(rootPath, tempFile)).catch(() => {})));
await node_fs_promises.writeFile(tempPath, content);
await node_fs_promises.writeFile(fullPath, content);
await node_fs_promises.unlink(tempPath).catch(() => {});
await node_fs_promises.unlink(tempPath).catch(() => {});
await fs.unlink(this.getFullPath(key));
await Promise.all(entries.filter((file) => file.endsWith(".tmp")).map((tempFile) => fs.unlink(path.join(rootPath, tempFile)).catch(() => {})));
await fs.writeFile(tempPath, content);
await fs.writeFile(fullPath, content);
await fs.unlink(tempPath).catch(() => {});
await fs.unlink(tempPath).catch(() => {});

Why it matters: Usually legitimate, but worth confirming the paths can't be controlled by untrusted input.

Fix: Confirm which files are written/deleted and that paths cannot be influenced by untrusted input.

Maintain langchain (npm)?

Check the next package before your agent installs it

The free Claude Code plugin scans each npm, PyPI or MCP package with this report's open-source engine before the install command runs. It runs on your machine and needs no account.

Check your own component

Run the same evidence-backed scan on any MCP server, agent skill, or package.

Scan your own component

How we determine this: deterministic static analysis (regex + AST), evidence-anchored, no code execution. Methodology →