2 findingsStatic scanned
Free
Framework for testing AI coding agents in isolated sandboxes
408.7k installs/moMIT
Agent Readability
vercel · Agent
Detect AI agents. Serve them markdown. Audit your site against the Agent Readability Spec.
Not claimed by its maker.
What else was checked
Publisher and name
Nothing found across 5 checks run. Checked 2026-10-04.
Maintenance
MaintainedLast release 4 Sep 2026 (0.7.0), 29 days before this check on 4 Oct 2026.
Read from the npm registry's publish history, read by the nightly publisher check.
Release activity only: it says nothing about quality or safety, and a finished small package can be fine without releases. How it is measured
- Tool description integrity
- nothing to read
- Pattern set 1.0 matched nothing on 2026-10-05, but none of the descriptions the package ships runs to 120 characters, so there was little for a rule to read.
- It reads the descriptions the package ships, not what the server says when it runs, and a clean description is not the same thing as a safe tool.
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.
Tool descriptions are read with pattern set v1.0, published with every rule, its sources and how often it has been wrong.
Receipt history: every signed receipt for every version of this listing, and what changed between them.
What it does
Detect AI agents. Serve them markdown. Audit your site against the Agent Readability Spec.
Compare with
Compare all 4How 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 0.7.0, the file with digest sha512-++aMEYribR25jInIv3QRBVhSmd2y7TscrtaO8YDaXbZjRcEaTWGgioaAtOl3a3VbzcgNl0VkiG59hn1yu/fNjQ==, as the registry publishes it. A published version cannot be replaced, so this names the same bytes for anyone who checks.
- Authentication
- Runs locally. No hosted endpoint is listed for this package. You run it on your own machine, so there is no endpoint of ours to authenticate against.
Adding it
Run it with:
npx -y @vercel/agent-readability@0.7.0Pinned to 0.7.0, 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.
238,524 installs last month (via ecosyste.ms) · no published advisories · version current · checked 2026-10-03
Where this came from
- Registry
- npm
- Package
- @vercel/agent-readability
- Version read
- 0.7.0
- Resolved
- 2026-09-23
No build provenance published. The repository above is the one the publisher declared, and nothing links it to the package you would install. That is not a mark against this listing, since most packages are published this way, but it is a check nobody can run.
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.
[](https://ooruby.com/market/vercel-agent-readability)About this listing
- Kind
- Agent
- Category
- Infrastructure
- Pricing
- Free
- Sandbox
- No
- Hosted
- No
- Updated
- 2026-09-04
More from vercel
See the storefrontSimilar agents
All agentsVerification 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.