@flashyos/countersign

A claim about you is not true until you sign it

Verification over a directory/1 record: a countersignature from the party a claim is about, an audit of what a website can prove, and a badge that carries a date. Ed25519 over the canonical assertion, verifiable offline from two published keys.

Why it exists

An organisation can publish an assertion about another one. This is what makes the other one’s agreement a verifiable fact rather than an unanswered claim: an Ed25519 countersignature over the canonical assertion, checkable offline from two published keys, by anyone, forever.

Use it

npx @flashyos/countersign audit https://example.com

Installing it puts these commands on your path — read from the package’s own manifest, so this list cannot drift from what you actually get.

The licence

Apache-2.0, read from the package’s own manifest. Embed it in anything, including closed software — that is what makes a spec adoptable and a verifier worth running. FlashyOS’s server side is AGPL-3.0-only instead, and a test in the monorepo asserts the direction between them: AGPL code may consume this, this may never consume AGPL code.

Keep reading