Skip to content

Validation Evidence

See which executable gates support the package, artifact, compatibility, and documentation claims.

The project treats evidence as part of the product contract.

Native category baseline

The pinned Oxlint binary materializes every configurable draft into an explicit rule map. Generated effective-config snapshots expose exact membership and make category changes visible during dependency upgrades. Tests verify the Essential, Recommended, and Strict category mapping, keep nursery disabled, and assert the generated rule counts.

Curated rule behavior

The behavioral harness runs valid and invalid fixtures through Oxlint for 27 curated ledger entries across 11 profiles. It also verifies that the AI option override changes real diagnostics instead of only changing JSON.

Scoped composition uses the same diagnostic evidence. Matching and nonmatching repository fixtures verify React + Vitest overlaps, runner isolation, Node script and configuration-file rules, declaration-only relaxations, retained required plugins, and consumer override precedence. Root effective-config snapshots remain limited to the prebuilt artifacts that Oxlint can materialize completely.

Configuration boundaries

Schema and ledger tests enforce:

  • Essential is a subset of Recommended, which is a subset of Strict;
  • identical base severity and options for curated rules shared between levels;
  • AI overrides only on already-active level rules;
  • no AI weakening, higher-level activation, or category widening; and
  • isolation of scoped runner and named experimental surfaces.

Package behavior

The package verifier builds and packs the project twice, checks deterministic bytes and exact tarball contents, installs the tarball into clean JavaScript and TypeScript consumers, verifies all public JSON exports, and exercises the public loader and customization APIs.

Supported matrix

CI runs the complete release gate on the documented Node.js, Oxlint, oxlint-tsgolint, and TypeScript versions. Separate consumers install and execute the built package on both supported Node lines.

Source evidence