Certification

Reliability certificates

Brunel measures one commit of a repository against a published criteria catalog, signs the result as an Open Badges 3.0 verifiable credential and publishes a badge anyone can verify.

A Brunel certificate is an automated, signed assessment of one commit of a repository against a public, versioned catalog of criteria. It is not an ISO certification, an accreditation, an audit or a security guarantee, and every public page and the credential itself say so.

What you get

  • A level (Bronze, Silver, Gold or Platinum) and a score out of 100.
  • The result of every criterion, with its evidence (paths, finding ids, counts).
  • A signed verifiable credential (Open Badges 3.0, Ed25519) that anyone can check offline.
  • A badge for your README and a verification page.
  • Optionally, a public company profile and a place in the ranking.

Issue a certificate

  1. Open the project of the repository in Brunel (a commit on its default branch).
  2. Choose Certify. The server downloads that exact commit and evaluates every criterion itself; the browser never sends a number.
  3. Review the result. The evaluation is kept on the server for 30 minutes; Issue signs it.
  4. Optionally Publish it: published certificates appear on the verification page with their evidence, on your company profile and in the ranking.

Who can certify: someone with proven access on GitHub, meaning any access to a private repository, or triage rights or more on a public one. Reading a public repository does not let a stranger certify it. Issuing, publishing, revoking and profile changes need a sign-in from the last two hours.

Validity and revocation

  • A certificate is valid for 90 days.
  • A tracked repository is re-evaluated on every push to its default branch: a commit that no longer meets the level revokes the certificate, and so does a repository that becomes inaccessible.
  • You can revoke a certificate at any time. Revocations are public, with their date and reason.

What is public

Only what you publish. For a published certificate: the repository name, commit, level, criteria and evidence. A private repository's name and evidence paths stay hidden until you publish. Members, conversations, tokens and your workspace never appear.

Read on: Criteria and levels and Badges and verification.

Reliability certificates · Brunel Docs