An offline, dependency-free checker for a JSON export of embedding metadata. It answers whether stored chunks still match the declared source digest and index contract, without loading a vector service or claiming that the underlying content is correct.
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/embedding-metadata-auditor.mjs --input examples/compatible.json --now 2026-01-01T00:00:00.000Z
node bin/embedding-metadata-auditor.mjs --input examples/incompatible.json --now 2026-01-01T00:00:00.000Z
npm run checkRead the result
The first command exits 0, the second exits 1. Both print exactly one JSON report. Programmatic callers can import audit and TOOLID from src/index.mjs; inject now as an instant, Date, or clock function. The CLI defaults to its own clock, overridable with --now in canonical UTC millisecond format.
Where this check stops
No embeddings are calculated, vectors validated, source files opened, index mutated, external account consulted, expiry renewed, or access authorization decided. This is an export consistency check, not a security grant or a claim about model behavior.
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.