Rate My GitHub

Profiles, repos, scores & roasts

← Rate my GitHub
jshchnz GitHub avatar

#33 · Top 96.9%

jshchnz

ɥsoɾ

B

Solid engineer

bronze medal

Overall

0.0

/ 100

Roasts

Category breakdown

jshchnz category score radarImpactConsistencyQualityDepthBreadthCommunity

Impact

25% weight

84A

The portfolio centers on practical developer tooling, scheduling, automation, cost control, evaluation, and AI-assisted workflows. Several project premises are distinctive and ambitious, though metadata alone cannot verify implementation or

Consistency

15% weight

82A

The supplied repositories show a dense pattern of recent updates from December 2025 through May 2026, with many distinct projects active in the same period.

Quality

25% weight

64C

Non-fork, non-archived status and repeated recent activity provide positive maturity signals, but the evidence excludes source, tests, CI, documentation, and architecture, so engineering quality can only be scored moderately.

Depth

20% weight

78B

Sixteen public repositories overall and multiple substantial-looking, actively updated projects indicate sustained ownership across a coherent tooling theme. Forked repositories are treated as weaker evidence of owned depth.

Breadth

10% weight

72B

The portfolio spans Python, Swift, TypeScript, Shell, and repositories with unspecified languages, covering automation, developer tools, AI workflows, infrastructure controls, and evaluation-oriented projects.

Community

5% weight

58D

Follower and star data provide a modest positive tie-breaker, with several projects showing visible interest. Popularity does not raise the other category scores, and zero-star projects remain neutral.

Stats

52-week commit heatmap

49 active days

Language distribution

  • Unknown50%
  • Shell17%
  • Swift17%
  • Python8%
  • TypeScript8%

Based on the bounded repository sample saved with this analysis.

Numbers

Owned repos

Non-fork sample

10

Commits

Last 12 months

2014

Followers

Accepted fact

62

Joined GitHub

Profile date

Feb 2014

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 jshchnz/sentry-mcp - An MCP server for interacting with Sentry via LLMs.
  3. Created jshchnz/mymcp - Discover, install and manage MCP servers on macOS
  4. Created jshchnz/claude-code-scheduler - Put Claude on autopilot
  5. Created jshchnz/tribute - Discover and fund the open source projects your code depends on
  6. Created jshchnz/claude-code-image
  7. Created jshchnz/claude-jobs - Claude Code skill for querying job openings at tech companies
  8. Created jshchnz/mcp_evals
  9. Created jshchnz/vercel-cost-guard
  10. Created jshchnz/refiner - A macOS app for data refinement
  11. Created jshchnz/codemaxxed
  12. Created jshchnz/codemaxxing
  13. Created jshchnz/sentry-workflows-plugin - Preview Sentry workflows for Claude Code — open fix PRs, groom stale issues, run as Claude Routines
  14. Most recent push to jshchnz/sentry-workflows-plugin

Compare

JSHCHNZ · 6DMEDIAN CODER

JSHCHNZ compared with MEDIAN CODER across six rating categoriesImpactConsistencyQualityDepthBreadthCommunity

Rubric

How this score was produced

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

CategoryWeightScoreContribution
Impact25%8421.00
Quality25%6416.00
Depth20%7815.60
Consistency15%8212.30
Breadth10%727.20
Community5%582.90
Impact · 84/100

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

Evidence for jshchnz. The portfolio centers on practical developer tooling, scheduling, automation, cost control, evaluation, and AI-assisted workflows. Several project premises are distinctive and ambitious, though metadata alone cannot verify implementation or

Quality · 64/100

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

Evidence for jshchnz. Non-fork, non-archived status and repeated recent activity provide positive maturity signals, but the evidence excludes source, tests, CI, documentation, and architecture, so engineering quality can only be scored moderately.

Depth · 78/100

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

Evidence for jshchnz. Sixteen public repositories overall and multiple substantial-looking, actively updated projects indicate sustained ownership across a coherent tooling theme. Forked repositories are treated as weaker evidence of owned depth.

Consistency · 82/100

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

Evidence for jshchnz. The supplied repositories show a dense pattern of recent updates from December 2025 through May 2026, with many distinct projects active in the same period.

Breadth · 72/100

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

Evidence for jshchnz. The portfolio spans Python, Swift, TypeScript, Shell, and repositories with unspecified languages, covering automation, developer tools, AI workflows, infrastructure controls, and evaluation-oriented projects.

Community · 58/100

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

Evidence for jshchnz. Follower and star data provide a modest positive tie-breaker, with several projects showing visible interest. Popularity does not raise the other category scores, and zero-star projects remain neutral.

Raw total
75.00
Top-end curve
+0.00
Final overall
75.0

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-10 · 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 10, 2026, 12:09 AM UTC and is marked aging.