parsley
Parser empire
You named the centerpiece parsley and then built enough surrounding infrastructure to make the herb aisle look like a compiler department.
Profiles, repos, scores & roasts
parsley
You named the centerpiece parsley and then built enough surrounding infrastructure to make the herb aisle look like a compiler department.
Repository binding unavailable
When one language was not enough to explain your parser obsession, you translated it into Haskell and kept going.
Historical result · no repository binding was retained
Repository binding unavailable
Most people collect design patterns; you turned parser-combinator patterns into their own research annex.
Historical result · no repository binding was retained
Repository binding unavailable
A dedicated parser debug app suggests the parsing machinery is important enough to deserve its own observatory—and possibly its own weather forecast.
Historical result · no repository binding was retained
Repository binding unavailable
The debug views project completes the classic toolchain arc: build the parser, build the debugger, then give the debugger a window seat.
Historical result · no repository binding was retained
Impact
25% weight
The portfolio centers on parser combinators and related tooling across Scala and Haskell, suggesting a distinctive and technically ambitious body of work with a coherent ecosystem.
Consistency
15% weight
The supplied repositories show substantial recent activity across 2025 and 2026, with multiple related projects updated over time and no archived entries in the listed set.
Quality
25% weight
Repository metadata supports strong signals from several non-fork projects, sustained activity, and specialized project clustering, but implementation quality and maturity details are unavailable.
Depth
20% weight
Repeated ownership of related parser projects across years, including core libraries and companion tooling, indicates sustained specialization and substantial continuity.
Breadth
10% weight
Meaningful variety is present across Scala and Haskell, including core libraries, integrations, debugging tools, and design-oriented work, though the overall focus is intentionally specialized.
Community
5% weight
Available community signals are a modest positive tie-breaker, with some repositories receiving notable interest; popularity is not used to raise the other category scores.
Based on the bounded repository sample saved with this analysis.
Non-fork sample
8
Last 12 months
55
Accepted fact
133
Profile date
Aug 2013
Scores marked Profile rating use bounded public repository metadata. Full repo analysis appears only when a separate accepted repository analysis exists.
j-mie6 /
86/100
A prominent, actively updated Scala parser project that appears to be a central portfolio work.
j-mie6 /
78/100
A substantial Haskell counterpart in the same parser-combinator area, showing cross-language ownership.
j-mie6 /
73/100
An actively maintained Scala project within the portfolio's parser-focused ecosystem.
j-mie6 /
72/100
An actively updated Haskell parsing project that broadens the parser-focused body of work.
j-mie6 /
68/100
A focused Haskell project on parser-combinator design patterns, with long-term evidence of maintenance.
j-mie6 /
65/100
A Scala integration project connected to the main parser ecosystem and updated recently.
j-mie6 /
62/100
A recently updated Scala debugging application supporting the broader parser-tooling theme.
j-mie6 /
55/100
A Haskell reference project maintained within the broader language and parsing-oriented portfolio.
j-mie6 /
48/100
A forked Scala debugging-view project with recent activity, but ownership signals are less clear from metadata alone.
j-mie6 /
42/100
A recently updated Scala fork related to the surrounding ecosystem; the fork status limits attribution confidence.
j-mie6 /
42/100
A recently updated Scala fork, useful as ecosystem context but not strong standalone evidence of original ownership.
j-mie6 /
42/100
A recently updated Scala fork that indicates engagement with a broader ecosystem, with limited ownership evidence.
How this score was produced
Overall = Σ(category × weight) + deterministic top-end curve
| Category | Weight | Score | Contribution |
|---|---|---|---|
| Impact | 25% | 84 | 21.00 |
| Quality | 25% | 78 | 19.50 |
| Depth | 20% | 88 | 17.60 |
| Consistency | 15% | 86 | 12.90 |
| Breadth | 10% | 64 | 6.40 |
| Community | 5% | 58 | 2.90 |
What it measures. Project usefulness, ambition, originality, and coherence. Popularity is not impact.
Evidence for j-mie6. The portfolio centers on parser combinators and related tooling across Scala and Haskell, suggesting a distinctive and technically ambitious body of work with a coherent ecosystem.
What it measures. Engineering and project-maturity signals supported by the available public metadata.
Evidence for j-mie6. Repository metadata supports strong signals from several non-fork projects, sustained activity, and specialized project clustering, but implementation quality and maturity details are unavailable.
What it measures. Sustained ownership, meaningful scope, and continued maintenance rather than one-shots.
Evidence for j-mie6. Repeated ownership of related parser projects across years, including core libraries and companion tooling, indicates sustained specialization and substantial continuity.
What it measures. Recency and contribution patterns across the supplied activity window.
Evidence for j-mie6. The supplied repositories show substantial recent activity across 2025 and 2026, with multiple related projects updated over time and no archived entries in the listed set.
What it measures. Language entropy and project-type diversity across owned repos.
Evidence for j-mie6. Meaningful variety is present across Scala and Haskell, including core libraries, integrations, debugging tools, and design-oriented work, though the overall focus is intentionally specialized.
What it measures. A weak positive tie-breaker for supplied community signals, never a popularity penalty.
Evidence for j-mie6. Available community signals are a modest positive tie-breaker, with some repositories receiving notable interest; popularity is not used to raise the other category scores.
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