Profiles, repos, scores & roasts
Repository binding unavailable
A CSS fork for a personal site is a perfectly respectable shortcut: the portfolio gets wheels before it gets an engine, and the repo is already dressed for the occasion.
Historical result · no repository binding was retained
Repository binding unavailable
Naming a repository after yourself is wonderfully direct—less a mystery box, more a digital nameplate waiting to reveal how much machinery is behind it.
Historical result · no repository binding was retained
Repository binding unavailable
The fresh push date says the project is alive; the fork says it may still be borrowing its personality, like a new outfit with the tags attached.
Historical result · no repository binding was retained
Repository binding unavailable
One repo handles the web-facing style while the other carries the profile banner: a compact portfolio ensemble, currently performing an opening act rather than a full festival set.
Historical result · no repository binding was retained
Impact
25% weight
The portfolio contains a personal-site-related fork and a profile repository, suggesting presentation-oriented goals, but the metadata provides limited evidence of distinctive usefulness or substantial scope.
Consistency
15% weight
Both listed repositories show recent push dates in October 2025, indicating recent activity, but the supplied metadata does not establish a longer contribution pattern.
Quality
25% weight
The repository metadata confirms one CSS project and one repository with an unknown language; it does not provide enough evidence to assess implementation quality or maturity deeply.
Depth
20% weight
Recent activity is visible in both repositories, but the supplied evidence does not establish sustained ownership, substantial scope, or maintenance history.
Breadth
10% weight
The two repositories represent a narrow visible project range: a CSS-language fork and a profile repository with unknown language.
Community
5% weight
No community traction is evidenced by the supplied metadata. Per the scoring rules, this is neutral rather than a penalty.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
1
Last 12 months
0
Accepted fact
0
Profile date
Mar 2023
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
p-vitharana /
32/100
A recently updated, non-archived profile repository with an unknown language; its apparent presentation purpose is clear from the name, but the available metadata cannot establish implementation depth.
p-vitharana /
28/100
A recently updated, non-archived CSS-language fork associated with a personal web presence; the fork status and limited metadata provide only modest evidence of original scope.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 35 | 8.75 |
| Quality | 25% | 35 | 8.75 |
| Depth | 20% | 30 | 6.00 |
| Consistency | 15% | 48 | 7.20 |
| Breadth | 10% | 28 | 2.80 |
| Community | 5% | 50 | 2.50 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for p-vitharana. The portfolio contains a personal-site-related fork and a profile repository, suggesting presentation-oriented goals, but the metadata provides limited evidence of distinctive usefulness or substantial scope.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for p-vitharana. The repository metadata confirms one CSS project and one repository with an unknown language; it does not provide enough evidence to assess implementation quality or maturity deeply.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for p-vitharana. Recent activity is visible in both repositories, but the supplied evidence does not establish sustained ownership, substantial scope, or maintenance history.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for p-vitharana. Both listed repositories show recent push dates in October 2025, indicating recent activity, but the supplied metadata does not establish a longer contribution pattern.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for p-vitharana. The two repositories represent a narrow visible project range: a CSS-language fork and a profile repository with unknown language.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for p-vitharana. No community traction is evidenced by the supplied metadata. Per the scoring rules, this is neutral 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-10 · rating-rubric/3
