Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 20:26 UTC

kschiess / parslet

A small PEG based parser library. See the Hacking page in the Wiki as well.

Ruby · HTMLMIT★ 840 stars⑂ 97 forkssince Mar 2010View on GitHub ↗

kschiess/parslet holds a health index of 26 out of 100, placing it in the At Risk band. It scores highest on Community & Adoption (70/100) and lowest on Vitality (13/100). It was last updated 1073 days ago. A single contributor accounts for most of its recent work.

26
overall / 100
At Risk

Software health index

Metrics are grouped into weighted categories on one standardized 1–100 scale. Overall starts as their weighted mean, calibrated against the distribution of the public record so bands carry percentile meaning; when public evidence triggers the High-Risk Jurisdiction Policy, the rating is adjusted and receives an At Risk ceiling of 34.

26
Exceptional93-100The record's top tier (≈ top 5%); essentially all checked criteria met
Excellent80-92Strong across the board; minor gaps
Good65-79Healthy; gaps are limited and manageable
Moderate50-64Acceptable with notable gaps; review recommended
Weak35-49Material weaknesses across several areas
At Risk20-34Significant weaknesses; adoption warrants caution
Critical1-19Severe problems (abandoned, single-maintainer, no hygiene)
VitalityCommunity &AdoptionSustainability &GovernanceEngineeringQualitySecurityAI Readiness

Score profile

Each axis is a category. The shape matters more than the average — a healthy subject fills the whole shape, while a spike-and-crater profile means strength in one dimension is masking risk in another.

The weighted overall 46 is calibrated to 44 on the published index scale (record calibration 2026-08-02).

Ownership

Kaspar SchiessPersonal account
94 followers26 public repossince Mar 2008

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsparslet2.0.0-222400 days ago

Metrics by category

Vitality

Is the project alive — is code being written and are releases shipping?

13Critical · 21% of overall
How it's scored
0/36Push recency — last push 1,073 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share1
days_since_last_push1,073
active_weeks_last_year0
How it's scored
16.2/27Ships releases — 10 version tags (no GitHub releases)
0/36Release recency — latest release 2,400 days ago
12.6/27Release cadence — a release every ~289.7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count10
latest_release_tag2.0.0
releases_from_tagsyes
days_since_latest_release2,400
mean_days_between_releases289.7
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: Signed-Releases. Remaining weights renormalized.

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

70Good · 17% of overall
How it's scored
47.4/60Stars — 840 stars
16.5/25Forks — 97 forks
6.4/15Watchers — 15 watchers
Inputs used
forks97
stars840
watchers15
growth_stateorganic
growth_factor_pct100
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges0
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services—
has_pull_request_templateno
How it's scored
80/80Total downloads — 83,488,858 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesparslet
dependents—
ecosystemsrubygems
total_downloads83,488,858
monthly_downloads—
unverified_packages_excluded—
Excluded from scoring (no data or not applicable): Registry dependents. Remaining weights renormalized.

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
2/22.5Commit distribution — top contributor authored 91% of commits
13.5/13.5Contributor breadth — 32 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled32
top_contributor_share0.91
How it's scored
36.8/42Issue resolution — 88% of issues closed
13.6/30PR acceptance — 44/97 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-Review — Found 6/22 approved changesets -- score normalized to 2
Inputs used
merged_prs44
open_issues16
closed_issues114
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.877
closed_unmerged_prs53
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.2/25Owner reach — 94 followers of kschiess
22.4/25Track record — 26 public repos, account ~18 yr old
Inputs used
followers94
owner_typeUser
is_verified—
owner_loginkschiess
public_repos26
account_age_days6,757
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
4/35Publish recency — latest publish 2,400 days ago
20/20Version history — 22 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesparslet
ecosystemsrubygems
any_deprecatedno
min_days_since_publish2,400

Engineering Quality

Are baseline engineering and documentation practices in place?

55Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — kschiess.github.com/parslet
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepagekschiess.github.com/parslet
docs_sitekschiess.github.com/parslet
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?

40Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-Review — Found 6/22 approved changesets -- score normalized to 2
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.4
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
14/35Direct dependencies free of known advisories — 1 affected: RedCloth 4.3.2 (high 7.5)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
33.7/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 1,194 days ago
Inputs used
sourceosv
advisories48
affected_packages7
assessed_packages51
unassessed_packages0
affected_by_severitycritical 3, high 4
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 51 resolved dependencies against OSV. This repository publishes no package the index resolves, so the repository dependency graph was assessed instead. That graph mixes development and test pins with shipped dependencies, so only the declared runtime dependencies are scored; transitive findings are reported as context and excluded from the score. Reachability is not analyzed.

AI Readiness

How well is the repo equipped to be developed and maintained with AI coding agents? Carries a deliberately small weight (4%): agent tooling is a real maintenance signal, but a repository with none can still reach 100/100.

42Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
18.7/40Legible commit history — 35 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.35
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/131 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes13,111
source_files_sampled131
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — example
Inputs used
example_dirsexample
has_mcp_signalno
api_schema_files—
interfaces_expected_of—
Excluded from scoring (no data or not applicable): API schema (OpenAPI/GraphQL/proto), MCP server. Remaining weights renormalized.

Key facts

840GitHub stars
32contributors
0commits, last 12 months
1,073days since last push
10releases
1bus factor
16open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • Star history carried forward from 2026-06-10: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 840 stars today.

More detail

Star and fork history 841 ★ / 97 ⇿
841Stars
97Forks
10Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

Star history is shown as collected on 2026-06-10. GitHub restricted the stargazers API to repository administrators in July 2026, so this series can no longer be extended; the current star total above remains live.

02004006008001,000840941592010-032018-042026-06
Major 1Minor 4Patch 5

Each point covers 15 days.

OpenSSF Scorecard 3.4 / 10
3.4aggregate

Independent, tool-agnostic security assessment from the open-source OpenSSF Scorecard. Each check rewards a security practice, not a specific vendor's tool. Checks Scorecard could not determine are marked n/a and excluded from the security score (never counted as zero).Scorecard v5.5.0 · 2026-09-12 20:26 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 6/22 approved changesets -- score normalized to 2
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
RubyGemsmiddleman—website/Gemfile
RubyGemsrb-fsevent—website/Gemfile
RubyGemsRedCloth—website/Gemfile
RubyGemsslim—website/Gemfile
RubyGemscod—website/Gemfile
RubyGemscase—website/Gemfile
RubyGemstext-highlight—website/Gemfile
RubyGemsparslet—website/Gemfile
RubyGemsrspec—website/Gemfile
All dependencies 51

Full resolved dependency set from the GitHub dependency graph: 9 direct and 42 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.

RegistryPackageVersionRelation
RubyGemscase0.5.2.1direct
RubyGemscod0.6.0direct
RubyGemsmiddleman4.3.5direct
RubyGemsparslet1.8.2direct
RubyGemsrb-fsevent0.10.3direct
RubyGemsRedCloth4.3.2direct
RubyGemsrspec3.9.0direct
RubyGemsslim4.0.1direct
RubyGemstext-highlight1.0.2direct
RubyGemsactivesupport5.0.7.2indirect
RubyGemsaddressable2.7.0indirect
RubyGemsbackports3.16.0indirect
RubyGemscoffee-script2.4.1indirect
RubyGemscoffee-script-source1.12.2indirect
RubyGemsconcurrent-ruby1.1.6indirect
RubyGemscontracts0.13.0indirect
RubyGemsdiff-lcs1.3indirect
RubyGemsdotenv2.7.5indirect
RubyGemserubis2.7.0indirect
RubyGemsexecjs2.7.0indirect
RubyGemsfast_blank1.0.0indirect
RubyGemsfastimage2.1.7indirect
RubyGemsffi1.12.2indirect
RubyGemshaml5.1.2indirect
RubyGemshamster3.0.0indirect
RubyGemshashie3.6.0indirect
RubyGemsi18n0.9.5indirect
RubyGemskramdown1.17.0indirect
RubyGemslisten3.0.8indirect
RubyGemsmemoist0.16.2indirect
RubyGemsmiddleman-cli4.3.5indirect
RubyGemsmiddleman-core4.3.5indirect
RubyGemsminitest5.14.0indirect
RubyGemspadrino-helpers0.13.3.4indirect
RubyGemspadrino-support0.13.3.4indirect
RubyGemsparallel1.19.1indirect
RubyGemspublic_suffix4.0.3indirect
RubyGemsrack2.2.2indirect
RubyGemsrb-inotify0.10.1indirect
RubyGemsrspec-core3.9.1indirect
RubyGemsrspec-expectations3.9.0indirect
RubyGemsrspec-mocks3.9.1indirect
RubyGemsrspec-support3.9.2indirect
RubyGemssassc2.2.1indirect
RubyGemsservolux0.13.0indirect
RubyGemstemple0.8.2indirect
RubyGemsthor1.0.1indirect
RubyGemsthread_safe0.3.6indirect
RubyGemstilt2.0.10indirect
RubyGemstzinfo1.2.6indirect
RubyGemsuglifier3.2.0indirect
Dependency advisories 7

This repository publishes no package the index resolves, so its own dependency graph was assessed — 51 packages, which also include development and test pins that never ship: 7 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
activesupport5.0.7.2indirectcritical68.1.2.1
kramdown1.17.0indirectcritical22.3.1
rack2.2.2indirectcritical333.2.6
RedCloth4.3.2directhigh14.3.3
addressable2.7.0indirecthigh22.9.0
concurrent-ruby1.1.6indirecthigh31.3.7
tzinfo1.2.6indirecthigh11.2.10

An advisory means the version recorded in the dependency graph falls inside an advisory’s affected range. Reachability is not analysed, and the graph includes development and test pins — a finding may concern tooling rather than shipped software.

Raw JSON report machine-readable

Feedback

Spotted something off in this report, or have thoughts to share? Wrong measurements, missed tooling, ideas, questions — anything is welcome. Every message is read and gets a response.

The message is kept through sign-in.

Scores are signals, not warranties. They reflect publicly visible practices on GitHub — not a code audit, and not a security guarantee.

Missing data is excluded and weights renormalized, never scored as zero. Methodology is versioned and open: metrics v2.10.0, schema v0.34.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statistics — RubyGems.