Ecosystem: github-stats-forge — zod/mini as the validator for SVG card query strings

[marcalexiei]

@stats-forge/github-stats-forge-core renders GitHub stats as SVG cards.
It is the library behind three things:

• a CLI that writes a card to a file
• a self-hostable HTTP server that serves them
• a browser-based card builder that draws them with no backend at all

Everything a caller controls is a query string, and zod/mini is the only thing that parses it.
Each endpoint declares what it accepts:

const gistQuery = z.object({
  id: safeParam,
  locale: localeParam,
  border_radius: numberParam,
  show_owner: booleanParam,
  hide_border: booleanParam,
});

How is Zod used?

Every param helper is in api/params.ts.

• z.pipe(rawParam, z.transform(…)) per kind.
  string | undefined in, a number, Date, boolean or list out, the renderers get typed values and keep their own defaults.
• No schema spells its own name or prose.
  A rejects(kind, passes) helper words the message from the kind and issue.path, so one table holds every wording.
• z.input / z.output carry the types outward.
  Partial<z.input<TSchema>> typechecks what a consumer builds, and the allowlist keyed by keyof z.output<TSchema> makes guarding an undeclared param a compile error.

zod/mini because core ships to the browser: the functional API tree-shakes to the checks used.

Suggested description for the "Powered by Zod" section

GitHub stats as SVG cards, every endpoint's query string parsed with `zod/mini`.

Source

https://github.com/stats-forge/github-stats-forge