ooruby: verified AI agents and MCP servers

Node Llama Cpp

Run AI models locally on your machine with node.js bindings for llama.cpp. Enforce a JSON schema on the model output on the generation level

Not claimed by its maker. Is this yours? Prove it and answer the findings

From the maker

From the README of node-llama-cpp 3.21.1

The registry now serves 3.22.1. Everything measured on this page describes 3.21.1.

Findings, provenance and the install command are records of the scanned version, not the one npm would give you today. Treat them as history until this listing is rescanned. Registry checked 2026-10-07.

Not yet tested

Data handling disclosed: finding; no statement of what it reads, writes or sends (README.md)

Published because it was found. A finding is information about where the limits are, not a verdict that the software is unsafe.

What this does not cover

Everything. Treat it as you would software from anywhere else.

Receipt history: every signed receipt for every version of this listing, and what changed between them.

What it does

Run AI models locally on your machine with node.js bindings for llama.cpp. Enforce a JSON schema on the model output on the generation level

Compare with

Compare all 4

How far this has been checked

Static scanned

What it establishes: Its published package, or for a hosted server its source repository at a recorded commit, was read file by file, without running it, by every check in our current scan.
What it does not: How it behaves when it runs, or anything the scan does not read yet: several rubric checks, the repository's history, and compiled code in folders named dist or build. For a hosted server, that the endpoint runs the code that was read. The ooruby Index sets out exactly what was read.
Exactly what was read: Version 3.21.1, the file with digest sha512-E3N0Ev2Va0wzydvXYFwM9Hvyo07PoWjt8T/9GMc43Cvt8YkV/NU/tYUgEMC1grTPv2o9PRjQi0G3Wb5P/awiMg==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.

How the rungs work

Adding it

Run it with:

npx -y -p node-llama-cpp@3.21.1 nlc

Pinned to 3.21.1, which is the version the findings above were found in. Drop the version to take whatever is newest, and the report on this page stops describing what you installed.

1,419,025 installs last month (via ecosyste.ms) · build provenance signed · runs a script on install · no published advisories · checked 2026-10-07

Where this came from

Registry: npm
Package: node-llama-cpp
Version read: 3.21.1
Resolved: 2026-09-23

Open the source

Built from source, attested

npm publishes a signed statement that this exact package was built from the repository below, at this commit. It is verifiable without taking our word for it.

Repository: github.com/withcatai/node-llama-cpp
Commit: 5b4ebc501213
Built by: github.com/actions/runner/github-hosted

The badge, if this is your listing

It renders the current rung (static scanned) and links back here, where what that does and does not establish is one click away. It updates itself as the evidence deepens.

[![ooruby: static scanned](https://ooruby.com/api/badge/node-llama-cpp)](https://ooruby.com/market/node-llama-cpp)

About this listing

Kind: App
Category: Developer tools
Pricing: Free
Sandbox: No
Hosted: No
Updated: 2026-09-12

Similar apps

Verification records what our published tests found on a specific version at a specific date. It is not a warranty, and it does not certify that software is free of defects.