01 · Roasts
1,216 Repos, 3 Stars — Quantity Speedrun
You have 1,216 public repositories and a grand total of 3 stars. That's a star-to-repo ratio of 0.002. At this rate you'll hit 1 star per repo sometime around the year 3,000.
The Scaffold Factory
At least 3 of 12 analyzed repos (zero-trust-passwordless-sdk, 1ntruder, graffiti-connect) are empty initializations pushed within seconds of creation. Your GitHub is less a portfolio and more a graveyard of `git init` commands.
CI? Never Heard of Her
Zero out of 12 repos have a CI pipeline. Not one. You've written resilience decorators in purecore-apify but apparently resilience doesn't extend to automated testing of your own code.
JavaScript Monoculture
83% of your codebase is JavaScript. TypeScript shows up at a rounding-error 0%. You've got the word 'TypeScript' in several repo names and READMEs but the actual bytes tell a different story.
FullAgenticStack & Vibe2Founder but 89 PRs to Nowhere
You fired off 89 PRs this year and opened exactly 1 issue. Your bio announces 'FullAgenticStack & Vibe2Founder' but the only project with a working framework (purecore-apify) has 0 stars and 0 forks. The vision is there; the audience hasn't arrived yet.
Built using
Zoral
Shadows one worker for a week, then takes over their job with zero extra setup. Behaves exactly like the original.
zoral.ai
02 · Category breakdown
- Impact25% weight56D
- Consistency20% weight65C
- Quality20% weight62C
- Depth15% weight55D
- Breadth10% weight40D
- Community10% weight55D
03 · Stats
365-day commit heatmap
203 active days
Language distribution
- JavaScript83%
- CSS10%
- HTML6%
- Stylus0%
- Pug0%
- TypeScript0%
- Other1%
04 · Numbers
Owned repos
non-fork
28
Commits
last 12 months
1,321
Followers
2,531
Joined GitHub
Apr 2009
05 · Top repos
suissa /
purecore-apify
Express-compatible framework with typed architecture, comprehensive docs, testing, resilience decorators, and AON observability. Shipped as working indie project with docs/ folder, ARCHITECTURE.md, and clean module structure.
suissa /
purecore-ninjalive
Personal P2P WebRTC video conferencing project with behavioral analysis. Typed code (vanilla JS), documented README, Docker Compose setup, but no tests/CI, unpolished codebase with incomplete implementations (truncated client/main.js), minimal adoption signals.
suissa /
one-harness-4-all
Early-stage TypeScript harness framework for AI agents with pluggable infrastructure. Strict types, semantic brands, documented architecture, but unproven adoption and thin test/CI coverage. Architectural scope is solid but execution remains speculative.
suissa /
r3q
CLI tool for syncing TypeScript type definitions between local projects and a user-global cache. Typed with tests and documented README, but pre-release (0.1.0), 0 stars, no production signals, and incomplete test suite.
suissa /
2factor.digital
A TypeScript demo of 2FA flow combining WhatsApp OTP + passkey with React frontend and Express backend using SQLite. Well-typed, documented, and structured, but experimental scope with no stars, tests, or CI—typical tutorial/portfolio proof-of-concept.
suissa /
Neo4jGateway
Neo4j Gateway API project with 34KB codebase, 66 commits over 2+ months, Apache license, README and tests present, but untyped JavaScript, no CI pipeline, and zero external adoption signals (0 stars/forks/watchers).
suissa /
Logmine
Anime tracking Chrome extension with 42 KB codebase, basic feature completeness (watch list, filtering, storage sync), but minimal production maturity: no tests, CI, license, or gitignore; created and completed same day (2026-04-11) with only 9 commits; untyped JavaScript in personal account context.
suissa /
vape_counter
Personal vaping tracker with React+TypeScript+Vite frontend and Node/MongoDB backend. Architectural scope adequate but shallow documentation, minimal tests, conflicted README, and very recent creation (2 days old, 4 commits) limit maturity.
suissa /
search0nGoogle-extension
VS Code extension scaffold with basic TypeScript typing and minimal test coverage. One-off commit with no README, undocumented API, and extremely recent creation (27 Apr 2026) with only 2 commits.
suissa /
graffiti-connect
Empty scaffold with minimal content: 2 KB repo, single commit, bare README title only, no source files or meaningful implementation.
suissa /
zero-trust-passwordless-sdk
Empty scaffold repo created 2026-04-16 with zero files, no README, no tests, no CI, no license. Single commit with no substantive code.
suissa /
1ntruder
Empty scaffold repository with zero commits, no files, no documentation, and no meaningful content. Created and immediately pushed with no actual work.
06 · Timeline
- Apr 20, 2009Joined GitHub
- Oct 16, 2025Created 2factor.digital — Autenticação via digital com navegador
- Nov 22, 2025Created purecore-apify — Express implementation in purecore way
- Nov 23, 2025Created r3q — Axios native implementation
- Dec 23, 2025Created purecore-ninjalive
- Feb 3, 2026Created Neo4jGateway — API Gateway para Neo4j
- Apr 11, 2026Created Logmine — extensão para guardar os animes que voce esta vendo e ja viu
- Apr 15, 2026Created 1ntruder — pentests
- Apr 16, 2026Created zero-trust-passwordless-sdk — Zero Trust Passwordless SDK
- Apr 17, 2026Created one-harness-4-all — One harness to rule them all
- Apr 24, 2026Created graffiti-connect
- Apr 24, 2026Created vape_counter — vapeeee
- Apr 27, 2026Created search0nGoogle-extension — search0nGoogle
- Apr 27, 2026Most recent push to search0nGoogle-extension
07 · Compare
08 · Rubric
How this score was produced
Overall = Σ (category × weight) + gentle top-end curve
Tier thresholds
▸ How the pipeline works
- 01Scrape.Pull every non-fork repo pushed in the last 90 days, plus your contribution calendar, followers, and language byte counts — straight from GitHub's REST & GraphQL APIs.
- 02Triage.A small model reads every repo's file tree + README and picks the 20 files per repo that actually reveal how you code.
- 03Grade each repo. All repos run in parallel through a fast scoring model that reads the picked files and rates each one independently on Impact, Quality, and Depth — with evidence citations.
- 04Aggregate. A larger reasoning model combines the per-repo scores with server-computed stats (heatmap, commit cadence, language entropy, follower count) to produce the 6-dimension profile score + roasts.
- 05Correct.Deterministic server-side checks enforce anchor-scale floors (e.g. a profile with 2,000+ public commits can't score 30 Consistency) and recompute the final verdict.
~90 seconds per profile, ~$0.25 in compute. Total of ~240 files read across your top-12 repos. One rating per GitHub account per day.
▸ Data sources & caveats
- Heatmap & commit totals: GitHub GraphQL
contributionsCollection— covers the last 365 days, includes private repos when the user has opted in (default). - Language %: byte totals across the top 30 owned non-fork repos.
- Curve: a small upward nudge centered on raw score ≈ 70, capping at 100. Prevents specialists from being unfairly penalised for narrow breadth.
- Anchor corrections: when server-measured signals (e.g. privateWorkLikely, multiRepoVolume, follower count) mandate a minimum category score, the aggregation step enforces it. These are signal-conditional, not identity-based floors.