Dev Legacy
Share your verified work history
Publish a privacy-preserving Dev Legacy profile for each GitHub organization you contributed to — built from real PR and review activity, not self-reported bullet points.
Get a Pullmaster Reviewer Score, performance trends, expertise areas, and an AI-written summary you can share with hiring managers. No code shared.
Aggregate metrics only. No code, repo names, or file paths shared.
What's on your profile
Each Dev Legacy page is a verified snapshot of your Pullmaster metrics at one organization.
Overall signal
Pullmaster Reviewer Score
A 0–100 score derived from your real pull request and review history, with a breakdown across five reviewer-strength components.
- File familiarity, path ownership, and semantic familiarity
- Author affinity and availability
- Based on at least 3 scored pull requests in the org
How you work
Performance pillars
Three aggregate pillars — productivity, review responsiveness, and review quality — each with supporting counts and monthly trend charts.
- PR volume, merge rate, and approval ratios
- Average review response time and assignment count
- Reviews given, approvals, and substantive feedback share
Where you know the code
Expertise areas
Code-area names where you are a primary owner or strong contributor, derived from Pullmaster ownership analysis across the org.
- Up to eight expertise areas per profile
- Primary owner or strong contributor badges
- Area names only — no file paths or repo names
For hiring managers
AI-written summary
A short professional summary written from your aggregate metrics and expertise areas — factual, verified, and grounded in Pullmaster data.
- 2–4 sentences highlighting your strongest signals
- Uses metrics only — no invented projects or code details
- Designed for sharing with managers and recruiters
What recruiters see
An illustrative preview of a public Dev Legacy profile.
@sarahchen
Contributions at Acme Corp · Jan 2023 to Jun 2026 · 4 repositories
Summary
Strong reviewer with deep familiarity across the auth and billing areas. Consistently responsive on review assignments with high-quality, substantive feedback on authored pull requests.
PULLMASTER Reviewer Score
87 / 100
Based on 24 scored pull requests
Productivity
82
Responsiveness
91
Review quality
85
Expertise areas
Verified by PULLMASTER · Aggregate metrics only · No code shared
Privacy-preserving by design
Dev Legacy shares aggregate Pullmaster intelligence — never your actual code or repository content.
What is shared
-
Pullmaster Reviewer Score and component breakdown
-
Productivity, responsiveness, and review quality metrics
-
Monthly trend charts
-
Expertise area names and role badges
-
AI-written professional summary
Never shared
-
Source code or file paths
-
Repository names
-
Pull request titles
-
Commit messages or review comment text
How it works
Dual opt-in — your org enables Dev Legacy, then you choose when to publish.
Org admin enables Dev Legacy
An organization admin turns on Dev Legacy for your GitHub org from the Pullmaster installations page. Developers cannot publish until the org opts in.
You publish your profile
Once you have at least 3 scored pull requests in that org, publish a Dev Legacy profile from your dashboard. One profile per organization you contributed to.
Share your public link
Copy your share link and send it to hiring managers or teammates. Published profiles refresh automatically, and you can revoke access anytime.
Build your verified Dev Legacy profile
Install Pullmaster on GitHub, enable Dev Legacy for your org, and publish a profile when you are ready to share your work history.
Free during early access. No credit card required.