salus
The One-Repo Portfolio
Salus is carrying the entire portfolio on its back: admirably focused, but also one README—or whatever evidence exists beyond the metadata—from becoming a full ensemble cast away from a solo act.
Roasts
Repository binding unavailable
JavaScript Solo Flight
A single JavaScript project is a clean commitment to one lane; now the portfolio just needs a few more lanes before the GitHub map stops looking like a very confident cul-de-sac.
Historical result · no repository binding was retained
salus
The Archived-But-Not-Archived Project
Salus is officially not archived, which means the door is still open; the visible activity, however, feels like the project stepped out for a long coffee in December 2023.
Category breakdown
Impact
25% weight
A single JavaScript project is evidence of a real project premise, but the supplied metadata does not reveal its usefulness, ambition, originality, or implementation scope.
Consistency
15% weight
One owned repository shows a past push in December 2023, with no broader contribution pattern supplied; the profile update date alone does not establish ongoing development.
Quality
25% weight
The repository is non-forked and non-archived, which modestly supports ownership and continued availability, but no code, tests, documentation, CI, or other maturity signals are available.
Depth
20% weight
A single owned project indicates some focused ownership, but repository metadata does not establish sustained scope, maintenance, or technical depth.
Breadth
10% weight
The portfolio contains one repository and one recorded language, so meaningful language or project-type variety is not demonstrated.
Community
5% weight
No community traction is shown, and unavailable or zero community signals are neutral rather than negative under the rubric.
Stats
52-week commit heatmap
0 active daysLanguage distribution
1 langs
- JavaScript100%
Based on the bounded repository sample saved with this analysis.
Numbers
Owned repos
Non-fork sample
1
Commits
Last 12 months
0
Followers
Accepted fact
0
Joined GitHub
Profile date
Jan 2023
Top repos
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
Timeline
- Joined GitHub
- Created fidelbermudez/salus
- Most recent push to fidelbermudez/salus
Compare
FIDELBERMUDEZ · 6DMEDIAN CODER
Rubric
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 38 | 9.50 |
| Quality | 25% | 35 | 8.75 |
| Depth | 20% | 30 | 6.00 |
| Consistency | 15% | 35 | 5.25 |
| Breadth | 10% | 25 | 2.50 |
| Community | 5% | 50 | 2.50 |
Impact · 38/100
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for fidelbermudez. A single JavaScript project is evidence of a real project premise, but the supplied metadata does not reveal its usefulness, ambition, originality, or implementation scope.
Quality · 35/100
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for fidelbermudez. The repository is non-forked and non-archived, which modestly supports ownership and continued availability, but no code, tests, documentation, CI, or other maturity signals are available.
Depth · 30/100
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for fidelbermudez. A single owned project indicates some focused ownership, but repository metadata does not establish sustained scope, maintenance, or technical depth.
Consistency · 35/100
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for fidelbermudez. One owned repository shows a past push in December 2023, with no broader contribution pattern supplied; the profile update date alone does not establish ongoing development.
Breadth · 25/100
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for fidelbermudez. The portfolio contains one repository and one recorded language, so meaningful language or project-type variety is not demonstrated.
Community · 50/100
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for fidelbermudez. No community traction is shown, and unavailable or zero community signals are neutral rather than negative under the rubric.
- Raw total
- 34.50
- Top-end curve
- +0.00
- Final overall
- 34.5
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
- 01
Validate. The server validates the login, signed browser session, attempts, cooldown, daily ceiling, and the single provider permit.
- 02
Collect. The VPS collector reads bounded public profile metadata and up to 12 recent repository metadata rows in volatile memory.
- 03
Rate. One pinned provider returned a closed profile-rating object with no tools, browsing, shell, or repository-content access.
- 04
Verify. Server checks bound the subject, rejected unsafe or echoed text, validated the schema, and recomputed rubric-v3 final arithmetic.
- 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-09 · 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 9, 2026, 9:08 PM UTC and is marked aging.