Verify a FundQuill document

Were you sent a FundQuill report, audit trail or assumption library? Check that it is intact and see which device signed it. The check runs in this browser tab. The document and your model are never uploaded, and you don't need a FundQuill license.

1. Choose the document

A .fundquill-report.json, .fundquill-audit-trail.json or .fqlib.json file.

Verify without this website

You don't have to trust this page to check a FundQuill document. The same checks are published as fundquill-check: open source (MIT), no dependencies, no network access, and tested against the same documents and verdicts as this page.

In a terminal or CI

npx fundquill-check report.fundquill-report.json model.xlsx --fingerprint <from the sender>

Exit code 0 means verified, 1 not verified.

Offline, in any browser

Download check.html from the latest release, compare its SHA-256 with the one in the repository's MANIFEST.md, and open it from your disk. It works with no network connection.

Source: github.com/mitikasha-llc/fundquill-check · npm: fundquill-check

What this check proves

  • Intact means every section covered by the hash chain is exactly as it was when the document was produced.
  • Signed means the device key embedded in the document signed it. A key is not a person: compare the signing-device fingerprint with the one the sender gives you through a channel you already trust.
  • It does not re-run the engine. The numbers are shown as they were produced. The engine version and engine SHA-256 record exactly which build produced them.