leopechnicki/endpoint-tester

Auto-discover API endpoints in your source code and guard against accidental removal. Fails CI if the number of routes drops below a saved baseline.

Trust Signals

name	description	required	default
directory	Directory to scan for endpoints.	no	./src
framework	Framework adapter to use (express, fastapi, spring, django, flask, fastify, koa, nestjs, hono, gin, echo, chi, nethttp). If omitted, endpoint-tester auto-detects from package.json / requirements.txt / pom.xml / imports.	no	""
baseline-file	Path to the baseline JSON file that records the known endpoint count. Created on first run.	no	.endpoint-tester-baseline.json
update-baseline	When "true", refresh the baseline file to the current endpoint count and commit it back to the repo (does NOT fail the run). Use this after an intentional endpoint removal.	no	false
version	endpoint-tester version to install. Use "latest" for the newest release, or pin to a specific version (e.g. "0.4.2") for reproducible CI.	no	latest
node-version	Node.js version used to run endpoint-tester. Must be >= 20.	no	20

name	description
endpoint-count	The number of endpoints discovered in this run.
baseline-count	The endpoint count recorded in the baseline (or "0" if none).
drift	One of: "ok" (count unchanged or increased), "added" (new endpoints detected), "removed" (endpoints missing — CI fails), or "no-baseline" (baseline file did not exist and was just created).