Prove which version of your tool someone has

When someone reports a problem with your tool, you need to know which files they actually have. This builder fingerprints each file in a package, so you can compare exactly what changed between checks.

Generate the manifest when you package the minimum, then keep it with the artifact hash and the environment you used when you test as a consumer. A new consumer can then use the package from its instructions, and the manifest identifies exactly what was checked.

It is the fingerprint step in the Turn a useful script into a Vibe guide. It runs locally from the command line with Python 3.10 or later, on Windows, macOS and Linux. Provider accounts, model weights, GPU compute and hosting are not included.