HumanReviewed.org
Conformance

Conformant verifiers and issuers.

Anyone may reimplement the standard. This page defines what an implementation has to do before it can call itself conformant. Requirement keywords follow RFC 2119: MUST, MUST NOT, SHOULD.

A conformant verifier

A verifier takes an attestation UID and produces a verdict. Its defining property is independence: the verdict is a pure function of chain state and the spec.

A conformant issuer

An issuer creates attestations. Its defining property is honesty about identity and content: it binds reviews to exact artefacts and never overstates who signed.

Reference implementations

The reference implementation is MIT-licensed TypeScript. Publication to the public npm registry is in progress; the package names below are the canonical ones.

@humanreviewed/spec

Types, the review-kind and signer-tier taxonomies, and canonical hashing (canonicalize, hashArtefact). The machine-readable half of the specification.

@humanreviewed/verifier

The reference verifier. Produces the seven-status verdict table, enforces tier integrity, and walks revision chains cycle-safe. Conformance means matching its verdicts.

@humanreviewed/eas-reader

An AttestationReader that resolves attestations from EAS on Base. Swap in any reader with the same interface to verify against your own node or indexer.