Profiles, repos, scores & roasts
Repository binding unavailable
You made searching files feel like a national infrastructure project, then apparently kept polishing it until the command line developed standards.
Historical result · no repository binding was retained
Repository binding unavailable
Most people rename one file and call it a day; this project looks at an entire media library and says, “What if chaos had a migration plan?”
Historical result · no repository binding was retained
Repository binding unavailable
The calendar was already complicated, so naturally you built another serious Rust project to make time itself submit to better tooling.
Historical result · no repository binding was retained
bttf
Bttf arrives with a name that sounds like a movie reference and the portfolio energy of a utility that expects you to know the backstory before asking questions.
toml
TOML looks friendly until someone maintains the serious implementation; then every punctuation mark gets its own governance process.
Impact
25% weight
The portfolio centers on widely useful systems, search, parsing, text, time, and data tooling, with several projects showing unusually strong public traction; usefulness and ambition are evident from the project set itself.
Consistency
15% weight
The supplied repositories show sustained recent activity across nearly every listed project, with dates extending through 2026 and a long profile history.
Quality
25% weight
Repository scope, longevity, language choices, and continued maintenance are strong engineering-maturity signals, though source, tests, CI, and implementation details are unavailable.
Depth
20% weight
Multiple non-fork repositories have long-lived ownership and recent updates, including a substantial cluster of related foundational libraries and major tools.
Breadth
10% weight
The listed work spans Rust and Go and covers search, parsing, file traversal, text processing, time, data formats, testing, and utilities, but remains concentrated in systems and developer tooling.
Community
5% weight
The supplied profile and repository metadata indicate substantial community reach and adoption, used here only as a modest supporting signal rather than as a substitute for project substance.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
12
Last 12 months
897
Accepted fact
13079
Profile date
Oct 2010
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
burntsushi /
96/100
A major Rust search utility with broad practical scope, sustained ownership, and unusually strong evidence of usefulness from its long-term activity and adoption.
burntsushi /
91/100
A dedicated Rust time library with meaningful scope and recent development, suggesting sustained investment in a foundational domain.
burntsushi /
88/100
A mature Go TOML project with substantial longevity, clear format-parsing relevance, and continued maintenance.
burntsushi /
87/100
A Rust CSV library with a broadly useful data-processing role, substantial longevity, and recent maintenance.
burntsushi /
86/100
A focused Rust library for character-oriented processing, maintained recently and positioned as reusable foundational tooling.
burntsushi /
84/100
A Rust pattern-matching library with foundational scope and sustained activity, fitting the portfolio's systems-tooling focus.
burntsushi /
84/100
A maintained Rust directory-walking library with durable utility and a focused, reusable scope.
burntsushi /
84/100
A long-lived Rust property-testing project with a clear developer-tooling purpose and ongoing maintenance.
burntsushi /
83/100
A maintained Rust byte-string-oriented library with specialized systems relevance and a clear place in the broader tooling cluster.
burntsushi /
78/100
A Rust project with an unusual name and sustained recent activity; the supplied metadata supports active ownership but gives limited detail about its purpose.
burntsushi /
72/100
A Rust globbing-related library with a focused premise and evidence of maintained ownership, though the supplied metadata shows a smaller apparent footprint.
burntsushi /
70/100
A practical Rust file-renaming utility with a distinctive domain premise and recent activity, narrower than the portfolio's foundational libraries.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 95 | 23.75 |
| Quality | 25% | 88 | 22.00 |
| Depth | 20% | 96 | 19.20 |
| Consistency | 15% | 96 | 14.40 |
| Breadth | 10% | 63 | 6.30 |
| Community | 5% | 86 | 4.30 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for burntsushi. The portfolio centers on widely useful systems, search, parsing, text, time, and data tooling, with several projects showing unusually strong public traction; usefulness and ambition are evident from the project set itself.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for burntsushi. Repository scope, longevity, language choices, and continued maintenance are strong engineering-maturity signals, though source, tests, CI, and implementation details are unavailable.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for burntsushi. Multiple non-fork repositories have long-lived ownership and recent updates, including a substantial cluster of related foundational libraries and major tools.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for burntsushi. The supplied repositories show sustained recent activity across nearly every listed project, with dates extending through 2026 and a long profile history.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for burntsushi. The listed work spans Rust and Go and covers search, parsing, file traversal, text processing, time, data formats, testing, and utilities, but remains concentrated in systems and developer tooling.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for burntsushi. The supplied profile and repository metadata indicate substantial community reach and adoption, used here only as a modest supporting signal rather than as a substitute for project substance.
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
