Profiles, repos, scores & roasts
Solid engineer
bronze medal
Overall
0.0/ 100
Repository binding unavailable
A Rust project with a five-digit star count is less a repository and more the portfolio’s elected head of state; every neighboring project now has to introduce itself as ‘also present.’
Historical result · no repository binding was retained
goldbach
Goldbach gets its own repository, because apparently casually wondering about a famous conjecture was not enough commitment; it needed version control and a mailing address.
Repository binding unavailable
The Swift project brings a whole new platform into the lineup, giving this portfolio the feel of someone collecting ecosystems the way other people collect browser tabs.
Historical result · no repository binding was retained
resume
The resume repository is the one project whose deliverable is literally evidence of the other projects, a beautifully recursive piece of portfolio infrastructure.
subagentmaxxing
‘Subagentmaxxing’ sounds like a startup pitch delivered at 2 a.m., but it also fits a portfolio that keeps turning niche technical ideas into standalone repositories.
Impact
25% weight
The portfolio includes a substantial Rust project, multiple focused mathematical and technical projects, developer tooling, a Swift application, and other distinctive personal projects. The range and visible interest suggest notable impact,
Consistency
15% weight
The supplied repositories show recent activity across nearly the entire visible set, with several projects updated in 2026 and continued work on an older 2025 project. The metadata supports a strong recent contribution pattern, though it is
Quality
25% weight
Languages, non-fork ownership, recent pushes, and a large flagship project provide positive maturity signals. However, the evidence excludes source, tests, CI, documentation, licensing, and architecture, so engineering quality cannot be
Depth
20% weight
The portfolio shows sustained ownership of many non-fork repositories, a high public repository count, continued maintenance, and at least one prominently established project. Metadata alone cannot establish implementation depth or long
Breadth
10% weight
The visible work spans Rust, TypeScript, Python, TeX, Swift, JavaScript, mathematical projects, developer-oriented tools, a resume, a website, and a fork. This is unusually broad in language and project type for the supplied sample.
Community
5% weight
The profile has substantial follower evidence and several repositories with nonzero stars, including one notably prominent project. Community signals are used only as a weak tie-breaker and do not determine the other category scores.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
11
Last 12 months
2122
Accepted fact
794
Profile date
Jan 2022
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
kuberwastaken /
86/100
A prominently established, actively updated Rust repository and the clearest flagship project in the supplied set.
kuberwastaken /
73/100
An older but still visible Python project with substantial external interest, suggesting durable relevance within the portfolio.
kuberwastaken /
72/100
An actively updated Swift project with substantial external interest, adding a distinct application and platform dimension.
kuberwastaken /
70/100
An actively maintained TypeScript project with visible external interest, suggesting a useful and continuing software effort.
kuberwastaken /
65/100
A recent Python project with an unusually ambitious name and a focused technical premise, though completion cannot be inferred.
kuberwastaken /
62/100
A recently updated Python reference-oriented project with some external interest and a potentially reusable purpose.
kuberwastaken /
58/100
A recent, owned Python project with a distinctive investigative premise; available metadata does not establish its implementation maturity.
kuberwastaken /
55/100
A recent Python project centered on a mathematically recognizable problem, indicating focused technical exploration.
kuberwastaken /
55/100
A recent Python project built around a major mathematical topic, showing a separate line of technical experimentation.
kuberwastaken /
53/100
A recently updated JavaScript personal website repository, providing a maintained presentation layer for the portfolio.
kuberwastaken /
48/100
A maintained TeX resume repository, useful as a personal artifact but narrower in software-project scope.
kuberwastaken /
35/100
A non-archived fork of VSCodium; it demonstrates ecosystem engagement, but fork status limits evidence of uniquely owned work.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 84 | 21.00 |
| Quality | 25% | 67 | 16.75 |
| Depth | 20% | 82 | 16.40 |
| Consistency | 15% | 86 | 12.90 |
| Breadth | 10% | 78 | 7.80 |
| Community | 5% | 62 | 3.10 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for kuberwastaken. The portfolio includes a substantial Rust project, multiple focused mathematical and technical projects, developer tooling, a Swift application, and other distinctive personal projects. The range and visible interest suggest notable impact,
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for kuberwastaken. Languages, non-fork ownership, recent pushes, and a large flagship project provide positive maturity signals. However, the evidence excludes source, tests, CI, documentation, licensing, and architecture, so engineering quality cannot be
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for kuberwastaken. The portfolio shows sustained ownership of many non-fork repositories, a high public repository count, continued maintenance, and at least one prominently established project. Metadata alone cannot establish implementation depth or long
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for kuberwastaken. The supplied repositories show recent activity across nearly the entire visible set, with several projects updated in 2026 and continued work on an older 2025 project. The metadata supports a strong recent contribution pattern, though it is
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for kuberwastaken. The visible work spans Rust, TypeScript, Python, TeX, Swift, JavaScript, mathematical projects, developer-oriented tools, a resume, a website, and a fork. This is unusually broad in language and project type for the supplied sample.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for kuberwastaken. The profile has substantial follower evidence and several repositories with nonzero stars, including one notably prominent project. Community signals are used only as a weak tie-breaker and do not determine the other category scores.
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-10 · rating-rubric/3