io.github.Hiper-AIPublished by GitHub account Hiper-AIv1.0.0Updated Nov 7, 2026
Version-accurate library docs for coding agents, with a supply-chain check of each dependency.
pinright's local MCP server; no sign-in required; STDIO; 6 tools.
No AI overview yet: these facts come from the registry entry and the server itself.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Version-accurate docs and a dependency check for coding agents. Your agent gets library versions from one of two places: its memory, where about 40% of the pins it wrote in our benchmark carried a known advisory, or a docs MCP server, which returns documentation and does not check the version against advisories. pinright gives it the docs for the exact version it installs and a verdict on every dependency it adds, before the install runs. MCP server, pre-install hook, CLI and GitHub Action, all local.
[npm] [CI] [License: MIT] [Install in Cursor] [Install in VS Code]
Node 20.9 or newer. One line, then restart the agent:
init wires the MCP server, the pre-install hook where the client has one, and a starter
.pinright.json. 16 clients; six have a hook: Claude Code, Cursor, VS Code (GitHub Copilot),
OpenAI Codex, Gemini CLI and Windsurf. The Cursor and VS Code buttons above add the MCP server
only. Every client, scopes and pinright doctor.
Without. The agent runs npm install [email protected]. It installs. The lockfile now carries
five advisories, two of them high, and nobody is told.
With. The hook answers before the command runs, and the agent reads this:
The agent retries with 4.18.1, on the same release line. When it asks first, check-package
and get-docs give it the same verdict with the full advisory list, the version to pin, and the
docs for that version. Real output of pinright hook claude, 2026-11-01.
Docs MCP servers return documentation for a library. They do not check the version the agent pins,
and they do not see the install. To measure that kind of server we ran pinright's own server with its
security layer off (PINRIGHT_ABLATION=docs-only): docs for the version asked, no verdict. It is not
another product. Claude Code with Sonnet 5.5, Haiku 5.5 and Opus 5.5, 2 runs per cell, on the 1.0.0
code; each cell gives the range over the three models.
Current docs alone removed most alerts; the verdict removed the rest. Per model, pinright used 21% to 26% fewer tokens than the docs-only server on the 12 agent tasks and 26% to 33% fewer on the 8 docs tasks. Every paired interval stays above zero; the lowest bound is 2%. Tokens count everything the model processed, cache reads included. No tools at all costs less than either.
Why fewer tokens. With docs only, the agent looked versions up through the docs: it called
get-docs once per package, 5.2 to 5.7 times per agent task, before writing a file. 87% of those calls
named no version, so they returned the docs of the latest release, and 75% asked for "version" or
"latest" in the query. With pinright, every agent-task run opened with check-packages for the whole
list, about 600 characters of verdicts and versions to pin, then called get-docs 0.7 to 1.7 times per
task, with a version in 86 of 87 calls.
Limits. The 0.3 left is nuxt, whose current release pulls packages with no fix published;
installing with no version gets the same 0.3, and the docs-only and pinright alert intervals overlap.
One vendor's models, tasks we wrote, no shell, two days of advisory data, small n. In a second run
with a shell, the agents looked versions up with npm view or pip index before pinning, and every
arm ended at the same 6 alerts per model: there pinright made no measurable difference to the pins.
On APIs released after August 2026, 2 of 48 runs got the current API without docs, 45 of 48 with docs
only and 46 of 48 with pinright. On 12 tasks taken from public GitHub issues, 25% to 29% of direct
pins carried an advisory without docs and none with pinright. The hook blocked or asked on 1.46% of 25,077 public commands and
misread 10 of 154,402 tool calls from a month of our own agent sessions.
Per-model tables ·
results and caveats ·
technical report ·
reproduce it
Ecosystems: npm, PyPI, Cargo, Go, Maven and Gradle, NuGet, RubyGems, Composer, GitHub Actions.
Verdicts never say ok when a source did not answer. A committed .pinright.json sets allow and
deny lists, license rules, severity threshold and what to do when a source is down.
How it works ·
the hook ·
team policy ·
CLI ·
GitHub Action
No account, no telemetry. pinright sends package names and versions to deps.dev, OSV, the registries, jsDelivr and GitHub, never your code; SECURITY.md lists each host. The hook reads commands and files statically: it is a guardrail, not a sandbox, and the threat model lists what gets past it. When a source is down the built-in default lets the install through; the starter policy asks instead.
Install · prompt injection · benchmark · security review · changelog · contributing · release runbook
The report we value most is a false positive: a command the hook blocked, or a package it
flagged, that should have passed. Open an issue with the template and paste the command and the
output of npx pinright doctor --json. Report a vulnerability in pinright privately, as
SECURITY.md describes.
MIT. Built by Hiper AI ([email protected]). Site: pinright.dev. Everyone taking part follows the Code of Conduct.
Source: README.md at commit db06565
Find a library (with security verdict)
Finds the registry package for a library name ("next.js" -> npm:next, "pytorch" -> pypi:torch) and returns ids for get-docs, with the newest version that has no known advisories (safe) and a verdict. Skip it when you know the registry name: get-docs takes "npm:next" or "pypi:requests" directly, and check-packages takes plain names.
queryrequiredecosystemlibraryNamerequiredDocumentation for the version you will use (security-checked)
Returns the documentation sections that answer your question, taken from the package at a specific version (its published files and its repo at the release tag) and the project site. Without a version it documents the newest version with no known advisories. With a vulnerable version it starts with a SECURITY NOTICE and documents the safe version on the same release line, so the code you write keeps working after the upgrade.
namequerytokensversionecosystemlibraryIdpackageNameCheck a package before installing it
Supply-chain verdict for one package, no docs: known advisories (CVE/GHSA, malware), deprecation, license, newest version with no known advisories, the safe version on the same release line as the one you pass, and typosquat lookalikes. For several packages use check-packages, one call for the whole list.
namerequireddetailversionecosystemrequiredCheck a whole dependency list in one call
Supply-chain verdict for up to 50 packages at once: one table row per package (verdict, version to pin, short reason) and the full notice only for the ones that need attention. Call it once with every dependency you plan to add, before writing the manifest, instead of one check per package. Packages already in the project are checked at their installed version when you omit it.
packagesrequiredecosystemAudit a whole dependency tree
Audits every package in a lockfile (direct and transitive) against OSV, the way Dependabot would, and says how to fix each finding: the direct upgrade on the same release line, the parent upgrade that clears a transitive one, or an override. Pass a project directory or a file path, or the file content with its name. Supported: package-lock.json, npm-shrinkwrap.json, pnpm-lock.yaml, yarn.lock, package.json, requirements.txt, poetry.lock, uv.lock, pdm.lock, pyproject.toml, Cargo.lock, Cargo.toml, go.mod, Gemfile.lock, packages.lock.json, gradle.lockfile, pom.xml, build.gradle, build.gradle.kts, libs.versions.toml, composer.lock, composer.json, requirements*.txt. Without a lockfile the tree is resolved through deps.dev. GitHub workflows (.github/workflows/*.yml, action.yml, or the directory) get an Actions check: advisories and SHA pinning.
pathcontentfileNameincludeDevWhat changes between two versions
Breaking changes, removed or renamed APIs, config and default changes, packages that split off, deprecations, and the advisories fixed, between the version a project uses and the one to move to. Sources: changelogs and GitHub release notes for the versions in between, migration guides when a major is crossed, and (npm) a diff of the exported .d.ts API. Call it before upgrading across a major, when a SECURITY NOTICE recommends a new major, or to fix a Dependabot PR. Without "to" it uses the version pinright recommends.
tofromquerytokenspackageecosystemlibraryId90% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
npm i -g pinright && pinright init --user # just you, every project; the hook starts in about 0.2 snpx -y pinright init # your team: writes project files you commitpinright blocked this dependency change:- [email protected] (npm) has 5 known advisories (CVE-2021-23337, CVE-2026-4800, CVE-2020-28500, HIGH). Use 4.x release 4.18.1: npm install [email protected]Change the version (or the name) and try again. check-package and get-docs from the pinright MCP server explain each case.