Between building an artifact and shipping it, plenty can change it: a partial copy, a stray log file, a rerun that quietly produced different bytes. A manifest pins exactly what the build produced, so a later step can prove the directory still holds it.
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
# record what the build produced
node bin/artifact-manifest-generator.mjs generate ./dist \
--build '{"id":"build-42","revision":"abc123"}' \
--output dist-manifest.json
# later, prove the directory still holds it
node bin/artifact-manifest-generator.mjs verify ./dist --manifest dist-manifest.jsonRead 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
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.