Rate My GitHub

Profiles, repos, scores & roasts

← Rate my GitHub
akarachen GitHub avatar

#30 · Top 97.3%

akarachen

button painter, string concatenator, log alchemist

B

Solid engineer

bronze medal

Overall

0.0

/ 100

Roasts

Category breakdown

akarachen category score radarImpactConsistencyQualityDepthBreadthCommunity

Impact

25% weight

78B

Several original, non-fork projects span infrastructure, developer tools, monitoring, engines, and Rust systems work. The visible portfolio suggests ambitious and potentially useful projects, while implementation substance cannot be judged.

Consistency

15% weight

88A

The supplied repositories show very recent activity across nearly the entire visible set, indicating an unusually active current contribution pattern. The evidence covers only listed dates, not the full historical record.

Quality

25% weight

66C

Multiple non-fork projects use TypeScript, JavaScript, Rust, and Shell, and several have nonzero visible stars. These are maturity signals only; the available metadata does not establish source code, tests, CI, documentation, architecture,


Depth

20% weight

79B

The number of non-fork projects, recurring recent updates, and several projects with meaningful visible interest suggest sustained ownership and scope. Long-term maintenance and implementation depth remain only partially observable.

Breadth

10% weight

83A

The portfolio includes systems-oriented Rust projects, TypeScript applications and tools, JavaScript infrastructure, Shell work, and varied project types. Forks are not counted as strong evidence of owned breadth.

Community

5% weight

52D

Follower and star data provide a modest positive tie-breaker, including 339 followers and a few repositories with visible stars, but popularity is intentionally not used to raise the substantive categories.

Stats

52-week commit heatmap

364 active days

Language distribution

  • TypeScript42%
  • Unknown25%
  • Rust17%
  • JavaScript8%
  • Shell8%

Based on the bounded repository sample saved with this analysis.

Numbers

Owned repos

Non-fork sample

9

Commits

Last 12 months

3933

Followers

Accepted fact

339

Joined GitHub

Profile date

Jun 2021

Top repos

Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.

Timeline

  1. Joined GitHub
  2. Created akarachen/hazuki
  3. Created akarachen/2code - The Vibe Coding Workstation — A desktop workspace where terminal, AI agents, and git live together for uninterrupted flow state
  4. Created akarachen/rabbithole
  5. Created akarachen/aghub - One hub for every AI coding agent. Unified configuration management for 22+ assistants.
  6. Created akarachen/inference-provider-registry
  7. Created akarachen/luna - Long-running coding-agent orchestrator for GitHub Projects
  8. Created akarachen/angel-engine
  9. Created akarachen/eric-way
  10. Created akarachen/slop-watch - Catalog of AI Slop — Astro + Content Collections
  11. Created akarachen/dashi-ppt-skill - An AI-agent skill that generates browser-editable presentations from multiple visual themes, exportable to HTML, PDF, and PPTX.
  12. Created akarachen/ghostty-studio - A visual Ghostty configurator that respects your config file
  13. Created akarachen/elective-system
  14. Most recent push to akarachen/elective-system

Compare

AKARACHEN · 6DMEDIAN CODER

AKARACHEN compared with MEDIAN CODER across six rating categoriesImpactConsistencyQualityDepthBreadthCommunity

Rubric

How this score was produced

Overall = Σ(category × weight) + deterministic top-end curve

CategoryWeightScoreContribution
Impact25%7819.50
Quality25%6616.50
Depth20%7915.80
Consistency15%8813.20
Breadth10%838.30
Community5%522.60
Impact · 78/100

What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.

Evidence for akarachen. Several original, non-fork projects span infrastructure, developer tools, monitoring, engines, and Rust systems work. The visible portfolio suggests ambitious and potentially useful projects, while implementation substance cannot be judged.

Quality · 66/100

What it measures. Engineering and project-maturity signals supported by the available public metadata.

Evidence for akarachen. Multiple non-fork projects use TypeScript, JavaScript, Rust, and Shell, and several have nonzero visible stars. These are maturity signals only; the available metadata does not establish source code, tests, CI, documentation, architecture,


Depth · 79/100

What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.

Evidence for akarachen. The number of non-fork projects, recurring recent updates, and several projects with meaningful visible interest suggest sustained ownership and scope. Long-term maintenance and implementation depth remain only partially observable.

Consistency · 88/100

What it measures. Recency and contribution patterns across the supplied activity window.

Evidence for akarachen. The supplied repositories show very recent activity across nearly the entire visible set, indicating an unusually active current contribution pattern. The evidence covers only listed dates, not the full historical record.

Breadth · 83/100

What it measures. Language entropy and project-type diversity across owned repos.

Evidence for akarachen. The portfolio includes systems-oriented Rust projects, TypeScript applications and tools, JavaScript infrastructure, Shell work, and varied project types. Forks are not counted as strong evidence of owned breadth.

Community · 52/100

What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.

Evidence for akarachen. Follower and star data provide a modest positive tie-breaker, including 339 followers and a few repositories with visible stars, but popularity is intentionally not used to raise the substantive categories.

Raw total
75.90
Top-end curve
+0.00
Final overall
75.9

Tier thresholds

S 90-100 Mass-producing humansA 80-89 Ship machineB 70-79 Solid engineerC 60-69 Getting thereD 40-59 README enthusiastF 0-39 GitHub tourist

I. How this saved profile rating was produced

  1. 01

    Validate. The server validates the login, signed browser session, attempts, cooldown, daily ceiling, and the single provider permit.

  2. 02

    Collect. The VPS collector reads bounded public profile metadata and up to 12 recent repository metadata rows in volatile memory.

  3. 03

    Rate. One pinned provider returned a closed profile-rating object with no tools, browsing, shell, or repository-content access.

  4. 04

    Verify. Server checks bound the subject, rejected unsafe or echoed text, validated the schema, and recomputed rubric-v3 final arithmetic.

  5. 05

    Save. Only a valid completion and allowlisted post-completion facts commit atomically; the public projection is then rebuilt.

This saved profile analysis is metadata-only and did not read repository trees, README files, or source code. Availability of new analysis is separate from this historical result.

Rated 2026-08-09 · rating-rubric/3

II. Data sources & caveats
  • Scores summarize one accepted, subject-bound analysis; they are not a security audit or endorsement.
  • Rank, percentile, and median use 1095 currently accepted public profiles and can change as the leaderboard changes.
  • Repository and language details reflect the bounded analyzed sample, not necessarily every repository.
  • Missing data is shown as unavailable or not evaluated instead of being inferred as zero.
  • Analysis completed Aug 9, 2026, 5:50 AM UTC and is marked aging.