Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-28 04:32 UTC

sparklemotion / nokogiri

Nokogiri (鋸) makes it easy and painless to work with XML and HTML from Ruby.

C · Ruby · JavaMIT★ 6,277 stars⑂ 942 forkssince Jul 2008View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sparklemotion/nokogiri holds a health index of 97 out of 100, placing it in the Exceptional band. It scores highest on Community & Adoption (96/100) and lowest on Sustainability & Governance (67/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.

97
overall / 100
Exceptional

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.

97
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 85 is calibrated to 97 on the published index scale (record calibration 2026-08-02).

Ownership

Sparkle MotionOrganization
74 followers11 public repossince Jun 2012

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsnokogiri1.19.4-1,18570 days ago

Metrics by category

Vitality

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

88Excellent · 21% of overall
How it's scored
36/36Push recencylast push 1 days ago
20.8/36Commit cadence30/52 weeks with commits
18/18Commit volume115 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year115
human_commit_share0.78
days_since_last_push1
active_weeks_last_year30
How it's scored
27/27Ships releases90 releases published
36/36Release recencylatest release 70 days ago
19.8/27Release cadencea release every ~50.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count90
latest_release_tagv1.19.4
releases_from_tagsno
days_since_latest_release70
mean_days_between_releases50.1
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?

96Exceptional · 17% of overall
How it's scored
60/60Stars6,277 stars
24.8/25Forks942 forks
12.1/15Watchers149 watchers
Inputs used
forks942
stars6,277
watchers149
growth_stateorganic
growth_factor_pct100

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges4
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, bestpractices.coreinfrastructure.org, ci.appveyor.com, github.com
has_pull_request_templateyes
How it's scored
80/80Total downloads1,251,966,672 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesnokogiri
dependents
ecosystemsrubygems
total_downloads1,251,966,672
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?

67Good · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.8/22.5Commit distributiontop contributor authored 56% of commits
13.5/13.5Contributor breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 98 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.564
How it's scored
40.4/42Issue resolution96% of issues closed
22.8/30PR acceptance1,084/1,424 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 1/6 approved changesets -- score normalized to 1
Inputs used
merged_prs1,084
open_issues79
closed_issues1,987
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d1
issue_closed_ratio0.962
closed_unmerged_prs340
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
30/30Ownership backingorganization-owned
0/20Verified domain
13.5/25Owner reach74 followers of sparklemotion
19.9/25Track record11 public repos, account ~14 yr old
Inputs used
followers74
owner_typeOrganization
is_verifiedno
owner_loginsparklemotion
public_repos11
account_age_days5,187

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 70 days ago
20/20Version history1,185 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesnokogiri
ecosystemsrubygems
any_deprecatedno
min_days_since_publish70

Engineering Quality

Are baseline engineering and documentation practices in place?

93Exceptional · 19% of overall
How it's scored
24/24CI workflows4 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests14 out of 15 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://nokogiri.org/
10/10Repository description
10/10Topics9 topics
10/10Wiki
Inputs used
topicsruby, nokogiri, xml, sax, ruby-gem, xslt, xerces, libxml2, libxslt
has_wikiyes
homepagehttps://nokogiri.org/
docs_sitehttps://nokogiri.org/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

84Excellent · 16% of overall

Security posture

80Excellent
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionno data
2.2/2.5CI-Tests14 out of 15 merged PRs checked by a CI test -- score normalized to 9
1.2/2.5CII-Best-Practicesbadge detected: Passing
0.8/7.5Code-ReviewFound 1/6 approved changesets -- score normalized to 1
2.5/2.5Contributorsproject has 98 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
5/5Packagingpackaging workflow detected
4/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
4/5SASTSAST tool is not run on all commits -- score normalized to 8
5/5Security-Policysecurity policy file detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate8
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages13
unassessed_packages3
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 13 resolved dependencies against OSV. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

87Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history74 of 78 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.949
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes864
How it's scored
18/18One-command bootstrapgumbo-parser/Makefile, gumbo-parser/src/Makefile
22/22Automated tests
11/11Lint / format config.rubocop.yml
11/11Static type checkingC (statically typed)
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance22 of the last 100 commits are automated dependency updates
8/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_filesgumbo-parser/Makefile, gumbo-parser/src/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.22
How it's scored
45/45Type-checkable codeC (statically typed)
53.8/55Manageable file sizes8/359 source files over 60KB
Inputs used
primary_languageC
largest_source_bytes708,902
source_files_sampled359
oversized_source_files8
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
Inputs used
example_dirsexamples
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

6,277GitHub stars
99contributors
115commits, last 12 months
1days since last push
90releases
1bus factor
79open 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-07-19: GitHub restricted the stargazers API to repository admins, so it can no longer be collected. The repository has 6277 stars today.

More detail

Star and fork history 6,276 ★ / 942 ⇿
6,276Stars
942Forks
90Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

Star history is shown as collected on 2026-07-19. 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.

01,2502,5003,7505,0006,2507,5006,276913202009-022017-112026-08
Major 0Minor 11Patch 69

Each point covers 17 days.

OpenSSF Scorecard 8.0 / 10
8.0aggregate

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-08-28 04:32 UTC

0Binary-Artifactsbinaries present in source code
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
9CI-Tests14 out of 15 merged PRs checked by a CI test -- score normalized to 9
5CII-Best-Practicesbadge detected: Passing
1Code-ReviewFound 1/6 approved changesets -- score normalized to 1
10Contributorsproject has 98 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 5 issue activity found in the last 90 days -- score normalized to 10
10Packagingpackaging workflow detected
8Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 8
8SASTSAST tool is not run on all commits -- score normalized to 8
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 1
RegistryPackageVersion constraintManifest
RubyGemsrdoc8.0.0Gemfile
All dependencies 16

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

RegistryPackageVersionRelation
RubyGemsmini_portile2indirect
RubyGemsminitest6.0.6indirect
RubyGemsminitest-mock5.27.0indirect
RubyGemsminitest-parallel_fork2.1.1indirect
RubyGemsraccindirect
RubyGemsrake13.4.2indirect
RubyGemsrake-compiler1.3.1indirect
RubyGemsrake-compiler-dock1.12.0indirect
RubyGemsrexical1.0.8indirect
RubyGemsrubocop-minitest0.40.0indirect
RubyGemsrubocop-packaging0.6.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsruby_memcheck3.0.1indirect
RubyGemsrubyzipindirect
RubyGemssimplecov1.1.1indirect
RubyGemsstandard1.56.0indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 13 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 3 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

No known advisories affect the assessed dependencies.

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 statisticsRubyGems.