Check it yourself
Every open check in a test report can be re-run by anyone, on the pack bytes you download, with public code. Here is how.
1. Get the tools
pip install "makerplane-data @ git+https://github.com/billmallard/makerplane-data"
This installs packtool. It needs Python 3.10 or newer and no account or key.
2. Download a pack
Use the Download button on the catalog, or fetch the URL
from manifest.json. Each catalog entry lists the pack's
sha256; sha256sum <file> should print the same value.
3. Re-run the checks
packtool report --check procedures-conus-2611.pack
With no other arguments, --check fetches the signed catalog, checks its
signature against the published key, matches your file to its entry by sha256, fetches
that edition's report.json and checks it against the catalog's
report_sha256. It then re-runs every open check and compares each check's
status and measured value, the row counts and the pack identity with the published
record. It exits 1 on any difference.
Offline, compare against a record you saved: --against report.json.
Some checks need more than the pack. They print as not reproducible here with the reason, not as a difference:
- checks against the previous edition need it:
--previous OLD.packor itsreport.json; - the four upstream-schema layers need the FAA CSVs the build read;
- device acceptance needs a pyEfis checkout (
--pyefis-src); - results from Auspex, a proprietary AI test engine, cannot be re-run outside. Each of its findings is printed with the location it names, so you can look at that place in the pack yourself.
4. Check the catalog signature by hand
The catalog is signed with an ed25519 key in minisign format. The public key is keys/minisign.pub in the repository:
minisign -Vm manifest.json -P RWQXjK7+q8WvsWtCd+QPQNxO7OcI5XuF1uxY7MGp+R2JidxFSO/20AR4
or, with the tools from step 1, packtool verify manifest.json --pub minisign.pub.
If your numbers differ
Please open an issue with the pack id and edition, the command you ran and its output. A published number that does not reproduce is a defect in the record or in the tool, and we want to know.
What this report is and is not
These are the checks we ran on this pack, what each one measured, and what each one cannot catch. It is evidence, not a warranty and not a certification. No authority has reviewed or approved this data or these checks. Passing them does not mean the data is correct, complete or current. Results marked as coming from Auspex come from a proprietary AI test engine whose method is not published; each of its findings is stated so you can check it yourself. This data is for Experimental / Amateur-Built use. This data is provided as-is with no warranty and any use of the data is at your own risk. Verify against official publications.