What's New in Dino
Releases and writing from the team. What your QA engineer has been working on.
Most API incidents aren't exotic exploits, they're the slow drift between what your API promises and what it actually does. Here's where that gap hides, and how to close it.
Past Dispatches
Documentation Refresh
The docs catch up to REST: docs.usedino.dev and every README rewritten, plus the v0.4.1–v0.4.4 release-pipeline hardening rolled up.
Read more →REST API Scanning
Dino now scans REST end to end: OpenAPI discovery, 19 fuzz strategies across 6 attack surfaces, response validation, and a real --fail-on-high CI gate.
Read more →Welcome to the Dino blog
This is your first Sanity-backed post on usedino.dev. Edit or delete it in Studio, then redeploy the static site.
Read more →CLI UX Patch
Fewer mystery failures: dino init warns before a bad URL, and scan timeouts now tell you what to do. Plus the groundwork for REST.
Read more →Rich Terminal UI
An Ink-powered terminal UI with a real design system, an ESM bundle a quarter of the size, and a tag-based release pipeline. Node 22 required.
Read more →Zero-Config Scanning
Point Dino at an endpoint and it just works: resilient introspection, operations generated from the live schema, and clean, pipeable output.
Read more →Socket.dev remediation
A security housekeeping release: four Socket.dev supply-chain findings remediated, and npm audit back to clean.
Read more →First public release
Dino is on npm as @dino-hq/cli. Install it globally, point it at a GraphQL endpoint, and get a real quality report in your terminal.
Read more →