SkillTotal

Is @langchain/core safe?

No malicious indicators - review capabilities before installing
Notable — review in context (capabilities are not malware):
  • Node.js filesystem write/delete
  • Node.js network egress

@langchain/core is an AI npm_package analyzed by SkillTotal's deterministic static scanner. The scan found no malicious indicators, though 2 risky constructs are reported for review. It can: filesystem write and network egress — capabilities are what the code can do, not a verdict on intent. Risk score 0/100 (low).

@langchain/core 1.2.13

npm_package · npm:@langchain/core
LOW
0
/ 100 risk score
Snapshot · scanned Sep 27, 2026 · @langchain/core@1.2.13 · engine 0.53.0 / ruleset 60

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

Capabilities — what this component can do (not a risk score):
filesystem writenetwork egress

Behavioral traits

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

Filesystem reach
Tool Execution Context
Network egress
Interaction & Communication / Direct Communication

Findings (2)

MEDIUMNode.js filesystem write/deleteST-FS-NODE-WRITE

The component writes or deletes files on disk.

* fs.writeFileSync("image.png", image);
* fs.writeFileSync("image.png", image);

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.

MEDIUMNode.js network egressST-NET-NODE

The component makes outbound network requests.

const res = await fetch(imageUrl);
const res = await fetch(imageUrl);
return this.call(() => fetch(...args).then((res) => res.ok ? res : Promise.reject(res)));
fetch(...args: Parameters<typeof fetch>): ReturnType<typeof fetch>;
return this.call(() => fetch(...args).then((res) => res.ok ? res : Promise.reject(res)));
if (!(encoding in cache)) cache[encoding] = caller.fetch(`https://tiktoken.pages.dev/js/${encoding}.json`).then((res) => res.json()).then((data) => new js_tiktoken_lite.Tiktoken(data)).catch((e) => {
if (!(encoding in cache)) cache[encoding] = caller.fetch(`https://tiktoken.pages.dev/js/${encoding}.json`).then((res) => res.json()).then((data) => new Tiktoken(data)).catch((e) => {

Why it matters: Usually legitimate, but confirm the destinations are expected and no sensitive data leaves.

Fix: Confirm the destination hosts are expected and that no sensitive data is sent off-host.

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 →