Platform coverage · filenames · checksums · references

Make the release prove its contract.

Define the files users should receive, paste a GitHub asset response or fetch one public release, and catch missing platforms, naming drift, empty uploads, duplicate names, broken references, and checksum gaps before the announcement.

Local by default: pasted data never leaves this page

Preflight input

Fetching contacts only GitHub's public API. Leave blank to work entirely offline with pasted JSON.

Patterns are JavaScript regular expressions. Match every filename from start to finish with ^ and $.

Required fields: release and required. Optional: checksumFiles and references.

Accepts a GitHub release API object, its assets array, or an array of {"name","size","digest"} objects.

Paste standard SHA-256 lines when the API does not provide asset digests.

Deterministic result

Release verdict

Load the synthetic sample or provide a contract and asset inventory.
Fixed-scope implementation

Put the contract in CI for US$49.

FirstPass turns one public repository's supported-platform promise into a versioned contract and a blocking GitHub Actions preflight, then proves both a passing fixture and a deliberately broken release fixture.

  • One public repository and one release workflow
  • Platform, architecture, filename, checksum, and documentation-reference rules
  • Machine-readable evidence artifact on every run
  • Passing and failing fixtures plus exact acceptance checks
  • One revision within seven days

Public intake first. Payment is requested only after fit and scope are confirmed. No repository write access or secrets are requested.

Why a contract

Green builds can still publish incomplete releases.

Declare coverageName every promised platform and architecture as an explicit filename rule.
Inspect the uploadValidate the actual release inventory—not a source checkout or pre-upload staging directory.
Keep evidenceExport a report that records the exact rules, assets, and failures behind the release decision.