Release an inspectable package of known bytes.
genesis-release-integrity · portable workflow
1Name the release inventoryscoped
2Inspect text content and identitiesscoped
3Create the reviewed manifestscoped
4Verify the consumer copyscoped
Workflow overviewRead · configure · verify
How it works
1
Name the release inventory
2
Inspect text content and identities
3
Create the reviewed manifest
4
Verify the consumer copy
Why it beats the alternative
This product
Copying a source tree into a ZIP
Inventory
Explicit files only
Broad directory copy
Identity
Reviewed and consumer manifests
No byte comparison
Screening
Hazards are reported for review
Private content may travel unnoticed
Boundary
Text inventory checks
Archives, binaries, and history need other tools
How it actually works
Exactly what it does — and when.
1Inspect only the files named in the release inventory
2Build a manifest of reviewed text bytes
3Compare the clean consumer copy with that manifest
In practice · A clean archive differs from the source tree
A maintainer reviews an explicit public-file inventory and creates its manifest. The extracted consumer archive then shows one changed README and one missing license, so release verification fails before publication.
Use it to…
Prepare a source release
Inspect a named text inventory before creating the public export.
Verify a clean consumer copy
Compare the downloaded or checked-out files with the reviewed manifest.
Screen a white-label package
Look for private markers in the explicit files and report what still needs separate review.
The shift it creates
Without it
- A broad export includes internal files
- Consumer bytes differ from reviewed bytes
- Heuristic screening is mistaken for complete secret detection
→
With it
- Publish from an explicit inventory rather than a broad copy
- Compare consumer files with the reviewed manifest
- Expose unsupported binary, archive, or history checks
What's inside
Allowlisted files
SHA-256 manifests
Consumer readback
MIT-licensed source
Who it's for
Open-source maintainers
need a sanitized, inspectable public export
Release engineers
need consumer bytes to match reviewed bytes
Teams shipping white-label source
need internal files kept out of the inventory
Questions, answered
✓ Instant delivery✓ Yours to own✓ Use on every project✓ Built to ship results
Ready to put Genesis Release Integrity to work?
Instant download · one-time price · own forever · all sales final
Genesis Release Integrity
Instant download · one-time price · yours forever