What is inspector built with?

inspector is a TypeScript repo built with Vite, React, Express, and Hono. It makes its content with yaml, papaparse, react-markdown, and remark-gfm, validates its data with Zod and Ajv, is tested with Vitest, ink-testing-library, and Testing Library, deploys with pino and @hono/node-server, and uses MCP. It has 465,914 written lines, with 717 test files.

Read on November 12, 2026, at commit 488c30d. Read it as markdown

The card says what it's built with. Its whole map opens it up: every part of the code and how it connects to the rest.

Frontend

The base 2

Interface 6

Icons 1

Backend

Support

Content 4

Validation 2

Testing 4

  • Vitest676 files
  • Testing Library147 files
  • Zod1 file
  • ink-testing-library1 file

Deploy 2

Tools 5

  • Storybook3 files
  • @vitejs/plugin-react1 file
  • chokidar1 file
  • tsdown1 file
  • commander6 files

Other 7

  • undici2 files
  • SemVer1 file
  • proper-lockfile2 files
  • @napi-rs/keyring1 file
  • atomically1 file
  • open1 file
  • strip-ansi1 file

Other repos with a similar stack

Ordered by how much of its stack they share with inspector, then by stars.

Frequently asked questions

What language is inspector written in?
inspector is written in TypeScript, with 465,914 written lines.
What framework does inspector use?
inspector is built with Vite, React, Express, and Hono.

The proof: in package.json

What services does inspector use?
Does inspector have tests?
Yes. inspector has 717 test files and is tested with Vitest, ink-testing-library, and Testing Library.
Which repos have a stack like inspector's?

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →