Rate My GitHub

Profiles, repos, scores & roasts

← Rate my GitHub
fstone GitHub avatar

#1072 · Top 2.1%

fstone

Fstone

F

GitHub tourist

red alert

Overall

0.0

/ 100

Roasts

Repository binding unavailable

Markdown couture

You gave WeChat Markdown its own CSS wardrobe, proving even plain text can arrive overdressed for the occasion.

Historical result · no repository binding was retained

Repository binding unavailable

The original homepage saga

A JavaScript GitHub Pages project from 2013: the web equivalent of finding an old mixtape and realizing the opening track is still surprisingly ambitious.

Historical result · no repository binding was retained

Category breakdown

fstone category score radarImpactConsistencyQualityDepthBreadthCommunity

Impact

25% weight

32F

The portfolio includes a personal website, dotfiles, CSS for WeChat markdown, and several forks, but the supplied metadata supports only modest evidence of distinctive or broadly ambitious original work.

Consistency

15% weight

24F

The visible activity is spread across 2013–2021, with no supplied repository updates after 2021; this suggests intermittent rather than sustained recent maintenance.

Quality

25% weight

34F

Two non-fork projects identify concrete technologies or artifacts—CSS and VimL—and there is a JavaScript personal site, but metadata does not expose implementation or maturity details.

Depth

20% weight

27F

The portfolio contains six repositories, but three are marked forks and the original projects show older update dates; metadata therefore supports limited evidence of sustained ownership or maintenance.

Breadth

10% weight

39F

The repositories span CSS, VimL, JavaScript, personal configuration, web publishing, and forked projects, providing meaningful though limited variety.

Community

5% weight

50D

The supplied profile has 32 followers and one repository star, but community signals are intentionally treated as a weak tie-breaker and do not materially change the assessment.

Stats

52-week commit heatmap

0 active days

Language distribution

  • Unknown50%
  • CSS17%
  • JavaScript17%
  • VimL16%

Based on the bounded repository sample saved with this analysis.

Numbers

Owned repos

Non-fork sample

3

Commits

Last 12 months

0

Followers

Accepted fact

32

Joined GitHub

Profile date

May 2009

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 fstone/dotfiles - my dotfiles
  3. Created fstone/fstone.github.io
  4. Created fstone/ncl-graphics-zh
  5. Created fstone/wechat-markdown-css
  6. Most recent push to fstone/tinacms.org
  7. Created fstone/tinacms.org - Organization site for general info, documentation, blogs & contribution guidelines.
  8. Created fstone/xtuple-client - Last fetched from upstream on Jan 4, 2019

Compare

FSTONE · 6DMEDIAN CODER

FSTONE compared with MEDIAN CODER across six rating categoriesImpactConsistencyQualityDepthBreadthCommunity

Rubric

How this score was produced

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

CategoryWeightScoreContribution
Impact25%328.00
Quality25%348.50
Depth20%275.40
Consistency15%243.60
Breadth10%393.90
Community5%502.50
Impact · 32/100

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

Evidence for fstone. The portfolio includes a personal website, dotfiles, CSS for WeChat markdown, and several forks, but the supplied metadata supports only modest evidence of distinctive or broadly ambitious original work.

Quality · 34/100

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

Evidence for fstone. Two non-fork projects identify concrete technologies or artifacts—CSS and VimL—and there is a JavaScript personal site, but metadata does not expose implementation or maturity details.

Depth · 27/100

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

Evidence for fstone. The portfolio contains six repositories, but three are marked forks and the original projects show older update dates; metadata therefore supports limited evidence of sustained ownership or maintenance.

Consistency · 24/100

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

Evidence for fstone. The visible activity is spread across 2013–2021, with no supplied repository updates after 2021; this suggests intermittent rather than sustained recent maintenance.

Breadth · 39/100

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

Evidence for fstone. The repositories span CSS, VimL, JavaScript, personal configuration, web publishing, and forked projects, providing meaningful though limited variety.

Community · 50/100

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

Evidence for fstone. The supplied profile has 32 followers and one repository star, but community signals are intentionally treated as a weak tie-breaker and do not materially change the assessment.

Raw total
31.90
Top-end curve
+0.00
Final overall
31.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, 9:10 PM UTC and is marked aging.