Docs / Reference

Open documentation actions
Raw MDXOpen on GitHub

Verified Combinations

See which Better Fullstack scaffold combinations currently have passing smoke, ScaffBench, release-guard, and published-package evidence.

Better Fullstack only treats rows with current Pass evidence as verified. The generated ledger is intentionally conservative: matrix-only and configured rows stay visible, but they are not counted as green claims.

Current verified claim

Generated Jul 3, 2026, 10:00 AM UTC.

Needs fresh release evidence

PR core smoke

smoke combinations

12/12

rows with Pass evidence

ownerpreset

Rerun: bun run test:smoke:pr-core

ScaffBench 2

validation runs

1/1

rows with Pass evidence

runnerowner

Rerun: bun run scaffbench:2:canonical

Release guard

missing evidence

Published package

package-manager installs for create-better-fullstack@latest

3/3

rows with Pass evidence

runnerpackage scriptcli package

Rerun: bun run test:published-package

What the claim covers

  • PR-core smoke presets with install, build, typecheck, and ecosystem-specific validation.
  • ScaffBench 2 canonical benchmark validation.
  • Release guard gates for schemas, templates, snapshots, AI examples, CLI/builder parity, web stack state, reproducible commands, add/history flows, and docs link validation.
  • Published package scaffolds through Bun, npm, and pnpm package-manager entrypoints when testing/.published-package/summary.json exists.

What it does not claim

  • Every theoretical stack combination is verified.
  • Configured or matrix-only rows are passing.
  • Package-manager registry installs beyond the package spec recorded in the published-package smoke artifact.

Each evidence card links to the source artifact, owner area, and rerun command. When a section is not fully passing, use those links in order:

  1. Open the source artifact and find the failing row or gate.
  2. Follow the owner link to the template, package, or test area responsible for that failure.
  3. Rerun the listed command after making a fix, then rebuild the verified-combinations ledger.

Source artifact

The detailed ledger is generated at docs/verified-combinations.md by:

bun run build:verified-combinations

To refresh the release-gate evidence before rebuilding the ledger, run:

bun run test:release:record

To refresh package-manager registry install evidence for the current published package, run:

bun run test:published-package

Badge endpoint

Use the Shields-compatible endpoint when you want to display the current verified count:

[![Verified combinations](https://img.shields.io/endpoint?url=https%3A%2F%2Fbetter-fullstack.dev%2Fapi%2Fverified-combinations)](https://better-fullstack.dev/docs/reference/verified-combinations)

The endpoint returns the aggregate Pass count across smoke, ScaffBench, release-guard, and published-package evidence.

Patreon