GitHub-verified certification
Journeymen grades your real projects against GitHub's server-side history — merged PRs, commit timestamps, authorship. Nothing self-declared survives unverified.
Skill badges are self-assigned. Endorsements are traded. Git history doesn't do favors.
02 — The grade
A blended 92/100 hides how much of it was checked. Every certificate separates what GitHub confirmed, what was cross-checked, and what was inferred — the three rows forming behind this text.
orbit-scheduler
@octocat · 847 commits · 23 PRs analyzed
03 — Method
Four moves. The graph behind you is now a single line — every step verified before the next.
01
journeymen auth login
One OAuth handshake with GitHub. The same identity everywhere — CLI, site, certificate.
02
journeymen analyze ./repo
Reads your local git history and shows you exactly what it found before anything leaves your machine.
03
journeymen submit
Everything GitHub can confirm — merged PRs, commit timestamps — is re-verified server-side. Your word is never the source.
04
certificate issued
A public, shareable record that states what was verified, cross-checked, and inferred. Never blended.
04 — Integrity
The lattice behind this section is the point: order under scrutiny. Four known attack vectors, each closed:
Commit SHAs and push timestamps are cross-checked directly against GitHub's server-side history.
Owned-repo work is always graded at a lower confidence tier than third-party-verified contribution.
PR credit is granted only by querying GitHub's actual PR object — never taken on the CLI's word.
Server-side AST analysis and a bounded code-quality LLM judgment score structure directly — not a self-reported claim.
05 — The record
One sign-in, one command, one certificate that holds up.
The graph you scrolled through just became our mark