Compare two comparable windows of an exported metric and report the pages whose recent window sits far enough below the baseline window to be worth a human look. Optional link and freshness exports are reported alongside the comparison, as context.
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-decay-detector.mjs --config examples/clean/decay.config.json # exit 0
node bin/content-decay-detector.mjs --config examples/broken/decay.config.json # exit 2Read the result
The broken project shows both halves of the contract in one run: /guides/install falls from about 62 to about 22 a day with 27 days of data in each window and is flagged as an error, while /blog/old-post has 30 sessions across five baseline days and is reported inconclusive rather than green. Because something was left unestablished, the run as a whole is incomplete.
Where this check stops
It also never writes anything, never fetches anything, and refuses any configured path that leaves the input root, by spelling or through a symbolic link.
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.