JST documentation

Project health and evidence

JST publishes evidence for its engineering claims. A badge is a link to the underlying run or registry record, not a substitute for review.

Signal	Evidence
Template validation	CI, browser matrix, security
Generated-project portability	create-jst CI on npm/pnpm and Linux/macOS/Windows
Published artifact	release canary, create-jst on npm
Architecture-policy performance	plugin benchmarks, plugin on npm
Showcase quality	CI, browser matrix, performance
Supply chain	OpenSSF Scorecard, npm provenance on each published version, immutable release tags
Supported combinations	jst.compatibility.json and compatibility guide
Bundle limits	npm run lint:budgets in the template and showcase release gates

What is measured

• CLI generation is exercised against both package managers on all three supported operating systems.
• Playwright covers SSR output, hydration, accessibility, and Chromium/Firefox/WebKit behavior.
• The policy benchmark records cold and cached wall time, CPU time, and peak memory against a reviewed baseline.
• Production dependency audits, CodeQL, dependency review, and provenance run independently of product tests.

JST does not collect runtime telemetry from generated applications. Download counts come from npm; contribution and response metrics come from public GitHub data.

This site is open source. Improve this page.