Contact
Open source · Content & Publishing

Content Identity Auditor

Check content identity collisions, canonical ownership and publication cadence with deterministic reports.

v0.1.0 · Node.js 22+ · MIT

Browse the public repository · View releases

The report is deterministically sorted, making it suitable for CI artifacts and release comparisons.

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

node ./bin/content-identity-auditor.mjs capture \
  --content=examples/catalog.json \
  --output=baseline.json \
  --captured-at=2026-08-20

node ./bin/content-identity-auditor.mjs audit \
  --content=examples/catalog.json \
  --baseline=baseline.json \
  --today=2026-08-20

Read the result

An audit exits with 0 when there are no blockers, 1 when the content gate is blocked, and 2 for invalid commands, unreadable input, or malformed data. Inputs are limited to 10 MiB.

Where this check stops

This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.

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.