Profiles, repos, scores & roasts
GitHub tourist
red alert
Overall
0.0/ 100
Repository binding unavailable
With one clearly non-forked project in the visible lineup, sde is carrying the original-work banner like a tiny Shell-powered flag in a very large fork parade.
Historical result · no repository binding was retained
nanoclaw
nanoclaw and its similarly themed neighbor make the portfolio feel ready to collect every small claw-shaped AI project—an ambitious zoo, even if the metadata leaves the cages unlabeled.
stripe-mock
stripe-mock is a wonderfully practical premise: all the drama of payments, none of the drama of real money—an appropriately cautious superhero origin story.
theia
A TypeScript fork named theia brings serious editor-platform energy to the shelf, like arriving at a tooling conference with a borrowed badge and excellent taste in venues.
Repository binding unavailable
terraform-buildkite and github-checks-buildkite-plugin suggest a determined tour through automation landmarks: one more pipeline-themed stop and the portfolio may qualify for infrastructure bingo.
Historical result · no repository binding was retained
Impact
25% weight
The portfolio includes infrastructure, developer tooling, payment-related projects, and newer AI-adjacent names, but available metadata provides limited evidence of distinctive owned outcomes.
Consistency
15% weight
The visible repositories span activity from 2015 through 2026, but most listed projects are forks and the supplied metadata does not show a sustained original contribution pattern.
Quality
25% weight
Languages and project types suggest exposure to Go, TypeScript, Python, JavaScript, Shell, and CSS, yet repository metadata alone cannot establish implementation quality or maturity.
Depth
20% weight
Only one listed repository is explicitly non-forked, while the remaining entries are forks; dates show some longevity but do not establish sustained ownership or scope.
Breadth
10% weight
The listed projects cover several languages and domains, including developer tooling, infrastructure, payments, web technology, and AI-adjacent projects.
Community
5% weight
Follower and star information is limited and neutral under the rubric; no strong community signal is available from the supplied metadata.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
1
Last 12 months
0
Accepted fact
15
Profile date
Mar 2012
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
yahuio /
48/100
The sole explicitly non-forked listed repository, using Shell and dating to 2021; it is the clearest signal of owned work, though scope is unknown.
yahuio /
29/100
A JavaScript fork maintained in the mid-2010s, indicating exposure to web technology without evidence here of distinctive ownership.
yahuio /
28/100
A Go fork with a payment-testing theme, a practical project premise whose engineering depth cannot be assessed from metadata.
yahuio /
28/100
A Go fork related by name to Terraform and Buildkite, suggesting infrastructure-tooling interests but limited evidence of original contribution.
yahuio /
27/100
A fork related by name to commerce tooling, with historical activity but no supplied evidence of original engineering scope.
yahuio /
27/100
A Python fork focused by name on build checks, representing developer-tooling exposure but limited demonstrated ownership.
yahuio /
27/100
A TypeScript fork connected by name to an editor or platform project, indicating ecosystem range but not standalone ownership.
yahuio /
27/100
A Go fork associated by name with networking or infrastructure, showing domain breadth without evidence of independent implementation.
yahuio /
25/100
A recent fork with an AI-adjacent name; the metadata shows recency but not original scope or implementation ownership.
yahuio /
25/100
Another recent fork in the same apparent AI-adjacent cluster, suggesting exploration but providing limited evidence of independent work.
yahuio /
25/100
A fork from 2023 with an AI-adjacent project name; its available metadata supports interest more than demonstrated independent impact.
yahuio /
25/100
A CSS fork with a compact name and 2020 activity; the metadata gives little basis for judging scope beyond a web-oriented project.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 32 | 8.00 |
| Quality | 25% | 35 | 8.75 |
| Depth | 20% | 24 | 4.80 |
| Consistency | 15% | 38 | 5.70 |
| Breadth | 10% | 47 | 4.70 |
| Community | 5% | 50 | 2.50 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for yahuio. The portfolio includes infrastructure, developer tooling, payment-related projects, and newer AI-adjacent names, but available metadata provides limited evidence of distinctive owned outcomes.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for yahuio. Languages and project types suggest exposure to Go, TypeScript, Python, JavaScript, Shell, and CSS, yet repository metadata alone cannot establish implementation quality or maturity.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for yahuio. Only one listed repository is explicitly non-forked, while the remaining entries are forks; dates show some longevity but do not establish sustained ownership or scope.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for yahuio. The visible repositories span activity from 2015 through 2026, but most listed projects are forks and the supplied metadata does not show a sustained original contribution pattern.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for yahuio. The listed projects cover several languages and domains, including developer tooling, infrastructure, payments, web technology, and AI-adjacent projects.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for yahuio. Follower and star information is limited and neutral under the rubric; no strong community signal is available from the supplied metadata.
Validate. The server validates the login, signed browser session, attempts, cooldown, daily ceiling, and the single provider permit.
Collect. The VPS collector reads bounded public profile metadata and up to 12 recent repository metadata rows in volatile memory.
Rate. One pinned provider returned a closed profile-rating object with no tools, browsing, shell, or repository-content access.
Verify. Server checks bound the subject, rejected unsafe or echoed text, validated the schema, and recomputed rubric-v3 final arithmetic.
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-11 · rating-rubric/3