explaingit

aminoxix/schemind

Analysis updated 2026-05-18

0TypeScriptAudience · developerComplexity · 2/5Setup · easy

TLDR

A library that watches your API responses at runtime, learns their shape automatically, and warns you when that shape changes without warning.

Mindmap

mindmap
  root((repo))
    What it does
      Learns API response shapes
      Flags breaking drift
      No schema to maintain
    Tech stack
      TypeScript
      Node.js
      Express
      Next.js
      Hono
    Use cases
      CI drift gate
      Slack alerts
      Type generation
    Audience
      Developers
      Ops teams

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Get alerted automatically when a backend API silently changes its response shape.

USE CASE 2

Add a CI gate that fails a build when an API introduces a breaking response change.

USE CASE 3

Generate TypeScript types, an OpenAPI spec, or mock handlers from real observed API responses.

USE CASE 4

Track both request and response shapes in an Express or Next.js backend with minimal setup.

What is it built with?

TypeScriptNode.jsExpressNext.jsHonoTanStack Query

How does it compare?

aminoxix/schemind0xradioac7iv/tempfs7vignesh/pgpulse
Stars000
LanguageTypeScriptTypeScriptTypeScript
Setup difficultyeasymoderatemoderate
Complexity2/53/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · easy Time to first run · 5min

Works as a drop-in fetch wrapper with zero runtime dependencies, though persisting baselines across restarts needs extra setup.

The README links to a LICENSE file but does not describe its terms in the text itself.

In plain English

Schemind watches the APIs your application calls and notices when their responses change shape, without you writing or maintaining a schema yourself. You wrap your existing fetch calls with a function it provides, and from then on it quietly learns what each endpoint actually returns. The first time it sees a response it stores that shape as a baseline, then it compares every later call against that baseline and tells you the moment something differs, such as a field disappearing, a type changing, or a value that used to always be present becoming allowed to be empty. Changes are grouped into three levels of severity. A field being removed or a type changing counts as breaking and gets flagged in red. A field becoming nullable or newly required is a warning shown in yellow. A brand new field being added is just informational and shown in blue. You can wire these observations into Slack, GitHub, or your own webhook so a teammate sees the alert instead of it sitting silently in a log. Beyond the plain fetch wrapper, the package includes ready made integrations for Express, Next.js route handlers, Hono, and TanStack Query, so you can drop it into common backend and frontend setups with minimal changes. It also ships a command line tool called schm that can run as a gate in continuous integration, probing your API and failing the build if a breaking change slipped through. That same tool can generate TypeScript types, an OpenAPI spec, JSON Schema, or mock handlers from what it has learned about your API, and it includes a small local dashboard for browsing endpoint health. By default the learned shapes live only in memory and reset when your app restarts, but you can persist them to disk so the same baseline is available the next time your CI pipeline runs. The package requires Node.js version 18 or later and has no runtime dependencies of its own. It works in the browser, at the edge, and in Node.

Copy-paste prompts

Prompt 1
Help me wrap my existing fetch calls with createSchemindFetch to start tracking API drift.
Prompt 2
Show me how to set up the schm CLI as a CI gate that fails on breaking API changes.
Prompt 3
Walk me through persisting schemind baselines to disk so CI has something to diff against.
Prompt 4
Explain how to generate TypeScript types from the API shapes schemind has observed.

Frequently asked questions

What is schemind?

A library that watches your API responses at runtime, learns their shape automatically, and warns you when that shape changes without warning.

What language is schemind written in?

Mainly TypeScript. The stack also includes TypeScript, Node.js, Express.

What license does schemind use?

The README links to a LICENSE file but does not describe its terms in the text itself.

How hard is schemind to set up?

Setup difficulty is rated easy, with roughly 5min to a first successful run.

Who is schemind for?

Mainly developer.

Open on GitHub → Explain another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.