Check whether a saved build manifest and captured response headers agree about how static assets may be cached. Long-lived immutable caching is useful for a content-addressed URL, but dangerous for a mutable URL such as index.js: clients may keep an old build after deployment. This tool reads exported evidence and reports that mismatch; it never requests a URL or changes a cache.
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
npm run check
node bin/static-asset-cache-auditor.mjs --input examples/clean.json
node bin/static-asset-cache-auditor.mjs --input examples/mutable-immutable-error.jsonRead the result
The first example exits 0 (pass); the second exits 1 (fail). Both use only synthetic example.test URLs. The tool does not resolve or fetch them.
Where this check stops
This is a reporter over exported headers and declarations, not a browser or CDN test. It cannot verify that a filename hash equals content bytes, that old deployments were purged, or that a real client revalidated. It does not fetch assets, inspect a live cache, infer policy intent from a filename, modify headers, or invalidate anything. Captures and manifest rows must be complete and trustworthy enough for the specific claim; unknown evidence is never a pass. The analysis timeout is cooperative, so a single synchronous filesystem operation cannot be interrupted mid-call.
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.