hello-world
The classic
hello-world is still here, bravely carrying the ancient tradition of proving that the keyboard works.
Profiles, repos, scores & roasts
#1058 · Top 3.4%
Shamly Mackey
☁️ Self-hosting addict | 🧠 AI tinkerer | 🌱 Farm tech dreamer. If it runs in Docker, it’s probably on my NAS.
GitHub tourist
red alert
Overall
0.0/ 100
hello-world
hello-world is still here, bravely carrying the ancient tradition of proving that the keyboard works.
appflowy-cloud-0.9.64
appflowy-cloud-0.9.64 sounds like a precise expedition into serious infrastructure—complete with a fork-shaped passport.
react-native-design
react-native-design promises a whole design universe in one repository name; the branding arrives before the evidence of the galaxy.
hsenidservlet
hsenidservlet has the energy of a Java web artifact that refuses to be retired, quietly keeping the server-side torch lit since 2016.
Impact
25% weight
There is some potentially useful project variety, including an app-related repository, demos, frontend work, and Java projects, but most repositories are forks or broadly named starter-style projects, limiting evidence of distinctive impact
Consistency
15% weight
The portfolio shows activity across 2016–2025, including recent pushes, but the supplied metadata does not establish sustained contribution patterns or continuity of ownership.
Quality
25% weight
Metadata supports some language and project-structure signals, but does not provide source, tests, CI, documentation, or other direct engineering-maturity evidence. The relatively high fork share further limits confident assessment of owned
Depth
20% weight
The profile contains 11 repositories, but 6 are marked as forks and the available metadata does not show sustained scope, release history, maintenance intensity, or implementation ownership.
Breadth
10% weight
The portfolio spans Python, SCSS, Java, HTML, JavaScript, and repositories with unknown languages, covering demos, frontend, application, and educational or contribution-oriented projects.
Community
5% weight
Community evidence is unavailable beyond six followers and zero listed stars; under the rubric this is treated as a neutral tie-breaker rather than a penalty.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
5
Last 12 months
0
Accepted fact
6
Profile date
Jun 2014
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
shamlymackey /
45/100
A standalone Java servlet project, providing the clearest metadata-level evidence of an independently owned application-oriented repository.
shamlymackey /
43/100
A standalone SCSS repository named about, offering evidence of a personal presentation or styling project but limited detail about its substance.
shamlymackey /
42/100
A non-fork frontend-oriented repository with an evocative design-system name; its standalone status is useful evidence, though the language is unavailable.
shamlymackey /
38/100
A standalone repository focused on coding standards, suggesting an engineering-practice theme, though its language and implementation scope are unavailable.
shamlymackey /
30/100
A recent fork named after an AppFlowy Cloud version; the metadata indicates current activity but does not establish original ownership or implementation depth.
shamlymackey /
29/100
A Python fork centered on demos; it suggests experimentation or learning use, while the metadata does not show independent scope.
shamlymackey /
28/100
A Java fork named jterm, with activity dating to 2018; the available metadata supports a terminal-related project theme but not independent development depth.
shamlymackey /
27/100
An HTML fork named patchwork, suggesting a web project or template-based experiment without metadata proving original scope.
shamlymackey /
26/100
A Java fork of teammates; its name suggests a larger application context, but the fork status and available metadata limit conclusions.
shamlymackey /
25/100
A standalone hello-world repository, which is a minimal portfolio signal rather than evidence of substantial project scope.
shamlymackey /
24/100
A JavaScript fork of first-contributions, aligned with onboarding or contribution practice rather than demonstrated original software ownership.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 32 | 8.00 |
| Quality | 25% | 38 | 9.50 |
| Depth | 20% | 30 | 6.00 |
| Consistency | 15% | 35 | 5.25 |
| Breadth | 10% | 48 | 4.80 |
| Community | 5% | 50 | 2.50 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for shamlymackey. There is some potentially useful project variety, including an app-related repository, demos, frontend work, and Java projects, but most repositories are forks or broadly named starter-style projects, limiting evidence of distinctive impact
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for shamlymackey. Metadata supports some language and project-structure signals, but does not provide source, tests, CI, documentation, or other direct engineering-maturity evidence. The relatively high fork share further limits confident assessment of owned
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for shamlymackey. The profile contains 11 repositories, but 6 are marked as forks and the available metadata does not show sustained scope, release history, maintenance intensity, or implementation ownership.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for shamlymackey. The portfolio shows activity across 2016–2025, including recent pushes, but the supplied metadata does not establish sustained contribution patterns or continuity of ownership.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for shamlymackey. The portfolio spans Python, SCSS, Java, HTML, JavaScript, and repositories with unknown languages, covering demos, frontend, application, and educational or contribution-oriented projects.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for shamlymackey. Community evidence is unavailable beyond six followers and zero listed stars; under the rubric this is treated as a neutral tie-breaker 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