01 · Roasts
Commit firehose
3,398 commits this year and a 360 multi-repo activity volume: the green squares are doing overtime.
Zero-star constellation
The portfolio ships 20+ named projects, but most sampled repos still show 0 stars and 0 forks. Distribution is the missing feature.
Test-suite selective
gift, pob, and .note brought tests; lo, stash, tikt, q, and liveboard left CI and tests on the backlog.
Platform-hopper
From Pob's Go/Swift/C/C# automation stack to lo-even glasses UI and Rust CLI tooling, this is far beyond another CRUD-only profile.
Built using
Zoral
Shadows one worker for a week, then takes over their job with zero extra setup. Behaves exactly like the original.
zoral.ai
02 · Category breakdown
- Impact25% weight68C
- Consistency20% weight80A
- Quality20% weight72B
- Depth15% weight65C
- Breadth10% weight80A
- Community10% weight80A
03 · Stats
365-day commit heatmap
281 active days
Language distribution
- JavaScript53%
- TypeScript15%
- Go11%
- CSS5%
- Shell4%
- C#3%
- Other9%
04 · Numbers
Owned repos
non-fork
53
Commits
last 12 months
3,398
Followers
25
Joined GitHub
May 2013
05 · Top repos
lhypds /
gift
A substantial JavaScript hooks server with four trigger types, a React dashboard, CLI tooling, and a focused Node test suite; adoption is unproven at 0 stars, but implementation depth and operational safeguards are strong.
lhypds /
pob
Pob is a substantial, documented Go desktop automation bridge with PSL macro execution, cross-platform native shells, MCP/HTTP control, binary frame IPC, and focused protocol and behavior tests.
lhypds /
lo-even
A documented, typed TypeScript Even G2 companion for lo with a substantial glasses UI, offline preview/drive tools, API integration, routing fallback, localization, and carefully measured pixel layout; adoption is not yet demonstrated.
lhypds /
lhypds
A maintained portfolio hub documenting 20+ named shipped projects and multiple live deployments, but this repository itself is primarily a README with no typed source, tests, CI, license, or gitignore.
lhypds /
.note
A documented Rust CLI for structured human-readable notes, with formatting, fuzzy search/open/delete, Markdown conversion, cross-platform installers, release packaging, and update support.
lhypds /
liveboard-mod-basic
A substantial, typed Liveboard module package with 13 registered modules, detailed README documentation, and careful browser integrations, but no visible tests, CI, license, stars, or external adoption evidence.
lhypds /
liveboard
A documented, typed React/Vite liveboard with modular card loading, persistent layouts, streaming AI edits, filesystem-backed data, and content-addressed image APIs; adoption is not yet evidenced by stars or forks.
lhypds /
stash
A substantial personal React/Express stash application with multi-platform URL analysis, authentication, screenshots, search, and sharing, but no visible adoption, tests, CI, license, or static typing.
lhypds /
timer
A documented, typed React/Vite timer with countdown, count-to, stopwatch, keypad, persistence, localization, and touch-oriented UI; it is thoughtfully structured but has no tests, CI, license, or visible adoption.
lhypds /
tikt
A polished but early-stage React/Express timeline app with SQLite persistence, authentication, localization, audio/location capture, and Mapbox-backed knot statistics, but no visible tests, CI, license, or adoption.
lhypds /
q
A functional JavaScript React/Express survey app with SQLite persistence, OpenAI survey generation, multilingual UI, scoring, charts, and streamed analysis, but no visible adoption or engineering automation.
lhypds /
lo
A substantial React/Express location social app with maps, weather, posts, messaging, marks, localization, and account sync, but currently has no visible adoption, tests, CI, license, or typed code.
06 · Timeline
- May 25, 2013Joined GitHub
- Jul 17, 2023Created .note — note is a format.
- Aug 19, 2023Created lhypds
- Jun 18, 2025Created timer — timer program.
- Apr 17, 2026Created gift — Webhooks.
- Apr 25, 2026Created q — Survey.
- May 26, 2026Created liveboard — Live board online.
- Jun 13, 2026Created liveboard-mod-basic — Basic liveboard modules
- Jun 27, 2026Created pob — Perception & Operation Bridge.
- Jul 20, 2026Created stash — Stashing things.
- Aug 1, 2026Created tikt — A tick tied in time.
- Aug 25, 2026Created lo — Your location.
- Aug 28, 2026Created lo-even
- Sep 2, 2026Most recent push to lo
07 · Compare
08 · Rubric
How this score was produced
Overall = Σ (category × weight) + gentle top-end curve
Tier thresholds
▸ How the pipeline works
- 01Scrape.Pull every non-fork repo pushed in the last 90 days, plus your contribution calendar, followers, and language byte counts — straight from GitHub's REST & GraphQL APIs.
- 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
- 03Grade each repo. All repos run in parallel through a fast scoring model that reads the picked files and rates each one independently on Impact, Quality, and Depth — with evidence citations.
- 04Aggregate. A larger reasoning model combines the per-repo scores with server-computed stats (heatmap, commit cadence, language entropy, follower count) to produce the 6-dimension profile score + roasts.
- 05Correct.Deterministic server-side checks enforce anchor-scale floors (e.g. a profile with 2,000+ public commits can't score 30 Consistency) and recompute the final verdict.
~90 seconds per profile, ~$0.25 in compute. Total of ~240 files read across your top-12 repos. One rating per GitHub account per day.
▸ Data sources & caveats
- Heatmap & commit totals: GitHub GraphQL
contributionsCollection— covers the last 365 days, includes private repos when the user has opted in (default). - Language %: byte totals across the top 30 owned non-fork repos.
- Curve: a small upward nudge centered on raw score ≈ 70, capping at 100. Prevents specialists from being unfairly penalised for narrow breadth.
- Anchor corrections: when server-measured signals (e.g. privateWorkLikely, multiRepoVolume, follower count) mandate a minimum category score, the aggregation step enforces it. These are signal-conditional, not identity-based floors.