Scoring Methodology & Mathematical Rules
How is the DevReality score calculated?
Scores are calculated by fixed rules in code, not by AI. They measure public presentation quality, not programming ability. Every point earned or deducted maps directly to observable public repository signals or PageSpeed Web Vitals.
- •Documentation completeness: README presence, quickstart guides, byte depth, and visual UI screenshots.
- •Repository hygiene: Clear project descriptions, topic tags, license files, and non-fork original ratio.
- •Portfolio quality: Core Web Vitals (FCP, LCP, CLS), responsive mobile viewport, and accessibility landmarks.
- •Discoverability: Profile pinned projects, clear naming conventions, and working live deployment URLs.
- •Real programming skill or system design: We never execute private code or assess algorithmic problem-solving.
- •Interview readiness or employment worth: Presentation scores do not predict job performance or engineering impact.
- •Private enterprise contributions: Developers with confidential enterprise repos naturally show lower public activity.
- •Team collaboration or soft skills: Public metrics reflect showcase presentation only.
GitHub Presentation Categories (100 Points Total)
Auto-generated from src/config/scoring.ts. Updated automatically with every score engine build.
| Category | Max Weight | What Is Checked & Evaluated |
|---|---|---|
| Profile Completeness | 15 pts | Bio presence, profile README existence, location, contact/website links, and avatar configuration. |
| Repository Presentation | 20 pts | Non-fork original project ratio, clear repository descriptions, topic tags, and tech stack clarity. |
| Documentation & Readability | 25 pts | README coverage across repositories, byte-size depth, installation commands, quickstart guides, and screenshots. |
| Maintenance Signals | 15 pts | Recency of latest repository push, active non-archived projects, and sustained commit consistency. |
| Technology Consistency | 15 pts | Cohesive primary languages, modern framework usage, and non-trivial codebase sizing (>2KB code bytes). |
| Discoverability & Pinned Repos | 10 pts | Showcase pinned repositories on public profile, descriptive repository names, and live homepage links. |
Portfolio Audit Categories (100 Points Total)
Evaluated using server-side DOM parsing and Google PageSpeed Insights API. Auto-generated from source code config.
| Category | Max Weight | What Is Checked & Evaluated |
|---|---|---|
| Performance & Web Vitals | 20 pts | Mobile & desktop PageSpeed metrics: First Contentful Paint (FCP), Largest Contentful Paint (LCP), and layout stability (CLS). |
| Accessibility (WCAG 2.2) | 15 pts | Semantic HTML landmarks (<main>, <nav>, <header>), image alt attributes, contrast ratios, and accessible form labels. |
| Search Engine Optimization | 15 pts | Descriptive <title> tags, meta descriptions, OpenGraph social preview tags, viewport tag, and valid heading hierarchy. |
| Security & Best Practices | 10 pts | HTTPS enforcement, modern HTML5 doctype, secure external link rel attributes (noopener/noreferrer), and clean DOM. |
| Project Showcase & Demos | 25 pts | Recognizable project showcase section, working live demo URLs, repository source code links, and narrative depth. |
| Mobile & Responsive Experience | 15 pts | Mobile viewport scaling, responsive layouts, media query structures, and touch-target friendly navigation. |
If a category cannot be inspected—such as when a portfolio URL is omitted, or when an external website blocks automated PageSpeed audit bots—DEV//REALITY does not penalize you with an arbitrary zero. Instead, the final score dynamically normalizes across all verified categories using the mathematical formula below:
Example: If only GitHub presentation is audited (100 max points available) and a candidate scores 82 points, their overall score is 82/100 (not diluted by the missing portfolio).
Confidence Levels
Every scored observation and recommendation is tagged with a transparent confidence level:
Directly Measured Data
Derived from definitive API fields or HTTP headers. Example: Repository count, README byte length, or PageSpeed First Contentful Paint.
Structural Pattern Matching
Derived from passive HTML/DOM inspections. Example: Presence of a <nav> landmark or matching regex patterns for live demo links.
Incomplete / Truncated Data
Derived from edge cases where an endpoint timed out or returned truncated metadata. Stated clearly so recruiters avoid unfair bias.
Score Bands & Qualitative Labels
| Range | Label | Description |
|---|---|---|
| 90 – 100 | Strong Presentation | Outstanding public technical presentation with clear documentation and attention to detail. |
| 75 – 89 | Solid Foundation | Good developer presence with a few areas that would benefit from polishing. |
| 60 – 74 | Needs Refinement | Core projects and profile are present, but presentation weaknesses dilute first impressions. |
| 40 – 59 | Major Improvements Needed | Noticeable documentation, organization, or portfolio gaps that hinder recruiter discovery. |
| 0 – 39 | Time for a Rebuild | Public technical presence is sparse, outdated, or incomplete. |
What Gemini AI Does:
- • Writes an entertaining roast based strictly on verified evidence IDs.
- • Simulates how a hiring manager scans your profile in 30 seconds.
- • Structures recommendations into an actionable redemption roadmap.
What Gemini AI NEVER Does:
- • Never calculates, modifies, or influences numerical scores.
- • Never invents repositories, features, or metrics outside verified evidence.
- • Never makes subjective character or personal trait judgments.
Want to see realistic reports in action?
Explore our sample reports or learn how the data collection pipeline functions.