Lint a directory of event declarations — names, owners, version sequences and versioned payload schemas — and check every version against the one before it under an explicitly chosen compatibility mode. Where a change breaks the mode, the report names the producers and consumers most likely to notice first, as candidates.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
npx event-schema-registry-linter --registry ./events --mode backwardRead the result
Inspect the command output and exit status against the README before treating the check as complete. The result depends on the supplied input and current release.
Where this check stops
maxDepth 8, maxEvents 500, maxFields 500, maxFileBytes 262144, maxSchemaDepth 12, maxVersions 50, timeoutMs 10000. Each has a command-line flag. Exceeding one produces an incomplete report with a finding naming the limit — never a quietly shorter answer.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.