Profiles, repos, scores & roasts
Repository binding unavailable
A personal website is the classic developer rite of passage: the project whose main feature is promising to explain the other projects someday.
Historical result · no repository binding was retained
Repository binding unavailable
With no language or description to give it away, this repository has achieved the rare status of being both public and dramatically enigmatic.
Historical result · no repository binding was retained
Repository binding unavailable
The HTML portfolio is laying the foundation for a grand personal brand—one div at a time, presumably with the future résumé waiting just offstage.
Historical result · no repository binding was retained
Repository binding unavailable
Paired with a portfolio site, the unnamed companion repository feels like a secret appendix: intriguing enough to notice, but not yet annotated for the reader.
Historical result · no repository binding was retained
Impact
25% weight
A personal website repository suggests a useful portfolio-oriented project, while the second repository has no supplied language or description to establish greater ambition or originality.
Consistency
15% weight
Two repositories are present, but the supplied dates show activity concentrated in 2024 with one later update in 2026; this is limited evidence of sustained contribution patterns.
Quality
25% weight
The non-fork, non-archived status provides a modest maturity signal, but the available metadata does not expose implementation quality, testing, documentation, or release practices.
Depth
20% weight
There are two owned repositories, including a personal website, but the metadata does not demonstrate substantial scope, long-term maintenance, or sustained ownership.
Breadth
10% weight
The portfolio contains an HTML project and one repository with unknown language; meaningful language or project-type variety is not established.
Community
5% weight
No community metrics are supplied beyond zero followers and zero stars; popularity is neutral here, so this score reflects unavailable evidence rather than a penalty.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
2
Last 12 months
233
Accepted fact
0
Profile date
Apr 2024
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
iridium99 /
32/100
An owned, non-fork, non-archived HTML repository for a personal website, with a later recorded push; its usefulness is apparent, but implementation and maturity cannot be assessed from metadata alone.
iridium99 /
20/100
An owned, non-fork, non-archived repository with unknown language and limited supplied activity evidence; its purpose, scope, and engineering substance remain unclear.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 28 | 7.00 |
| Quality | 25% | 30 | 7.50 |
| Depth | 20% | 20 | 4.00 |
| Consistency | 15% | 24 | 3.60 |
| Breadth | 10% | 12 | 1.20 |
| Community | 5% | 50 | 2.50 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for iridium99. A personal website repository suggests a useful portfolio-oriented project, while the second repository has no supplied language or description to establish greater ambition or originality.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for iridium99. The non-fork, non-archived status provides a modest maturity signal, but the available metadata does not expose implementation quality, testing, documentation, or release practices.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for iridium99. There are two owned repositories, including a personal website, but the metadata does not demonstrate substantial scope, long-term maintenance, or sustained ownership.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for iridium99. Two repositories are present, but the supplied dates show activity concentrated in 2024 with one later update in 2026; this is limited evidence of sustained contribution patterns.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for iridium99. The portfolio contains an HTML project and one repository with unknown language; meaningful language or project-type variety is not established.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for iridium99. No community metrics are supplied beyond zero followers and zero stars; popularity is neutral here, so this score reflects unavailable evidence rather than a penalty.
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-09 · rating-rubric/3
