FIGURE · ecosystem-tests
private backends, executed
354 passing across three repositories
- How it was taken
- Executed gates (runtime): npm test in ecosystem-core (242 passed at 1f1be6e, full verify chain exit 0), ecosystem-auth (28 passed), and content-management, the Supabase CMS with an MCP surface (84 passed across 6 files).
- Measured
- 2026-10-22
- Reproducible
- No: taken on the private host; a walkthrough is available on request.
What the number is made of
ecosystem-core
A versioned TypeScript SDK carrying semver, dist, ghost and consumer checks; 242 tests and a full verify chain exit 0.
Private component. Described, not linked; a walkthrough shows it.
ecosystem-auth
A better-auth integration whose suite is larger than its source tree: 209 test files against 8 source files.
Private component. Described, not linked; a walkthrough shows it.
content-management
A Supabase CMS with an MCP surface (84 tests), the same protocol surface this site sells.
Private component. Described, not linked; a walkthrough shows it.
A review
NDA review shows the repositories, the gates and the verify chain live.
Private component. Described, not linked; a walkthrough shows it.
How to check it
Closed source: nothing on this site links these repositories. The gates are reviewable under NDA, which is the honest form; naming the constraint is what makes the claim checkable later. One of the three already speaks MCP, the same protocol the offers sell.
Where this site cites it
- case study ecosystem backends