Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 14:28 UTC

st0012 / ruby-lsp-rspec

A Ruby LSP addon for RSpec tests

RubyMIT★ 218 stars⑂ 24 forkssince Sep 2023View on GitHub ↗

st0012/ruby-lsp-rspec holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (68/100) and lowest on Security (42/100). It was last updated 136 days ago. A single contributor accounts for most of its recent work.

62
overall / 100
Moderate

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.

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

Ownership

Stan LoPersonal account
612 followers79 public repossince Jul 2013@Shopify @ruby

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
RubyGemsruby-lsp-rspec0.1.29-30136 days ago

Metrics by category

Vitality

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

47Weak · 21% of overall
How it's scored
9.9/36Push recencylast push 136 days ago
4.2/36Commit cadence6/52 weeks with commits
10.3/18Commit volume13 commits in the last year
0/10OpenSSF Scorecard: Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year13
human_commit_share
days_since_last_push136
active_weeks_last_year6
How it's scored
27/27Ships releases29 releases published
27/36Release recencylatest release 136 days ago
19.8/27Release cadencea release every ~46.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count29
latest_release_tagv0.1.29
releases_from_tagsno
days_since_latest_release136
mean_days_between_releases46.9
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?

66Good · 17% of overall
How it's scored
37.9/60Stars218 stars
11.3/25Forks24 forks
3.3/15Watchers5 watchers
Inputs used
forks24
stars218
watchers5
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (MIT)
0/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_services
has_pull_request_templateno
How it's scored
71/80Total downloads6,782,738 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesruby-lsp-rspec
dependents
ecosystemsrubygems
total_downloads6,782,738
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.9/22.5Commit distributiontop contributor authored 78% of commits
13.5/13.5Contributor breadth12 contributors
10/10OpenSSF Scorecard: Contributorsproject has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled12
top_contributor_share0.784
How it's scored
23.4/42Issue resolution56% of issues closed
25.8/30PR acceptance55/64 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 10/30 approved changesets -- score normalized to 3
Inputs used
merged_prs55
open_issues16
closed_issues20
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.556
closed_unmerged_prs9
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
20/25Owner reach612 followers of st0012
25/25Track record79 public repos, account ~12 yr old
Inputs used
followers612
owner_typeUser
is_verified
owner_loginst0012
public_repos79
account_age_days4,744
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on rubygems
35/35Publish recencylatest publish 136 days ago
20/20Version history30 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesruby-lsp-rspec
ecosystemsrubygems
any_deprecatedno
min_days_since_publish136

Engineering Quality

Are baseline engineering and documentation practices in place?

68Good · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
10/20OpenSSF Scorecard: CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics3 topics
10/10Wiki
Inputs used
topicsrspec, ruby-lsp, vscode-extension
has_wikiyes
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

42Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.2/2.5CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 10/30 approved changesets -- score normalized to 3
2.5/2.5Contributorsproject has 4 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintained0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
2.2/7.5Vulnerabilities7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

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.

61Moderate · 4% of overall
How it's scored
45/45Agent instructionsCLAUDE.md
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes1,781
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config.rubocop.yml
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency 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_configyes
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/21 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes14,508
source_files_sampled21
oversized_source_files0

Key facts

218GitHub stars
12contributors
13commits, last 12 months
136days since last push
29releases
1bus factor
16open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-07-20 14:28 UTC

10Binary-Artifactsno binaries found in the repo
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
5CI-Tests13 out of 23 merged PRs checked by a CI test -- score normalized to 5
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 10/30 approved changesets -- score normalized to 3
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate 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
3Vulnerabilities7 existing vulnerabilities detected
Direct dependencies 10
RegistryPackageVersion constraintManifest
RubyGemsrake~> 13.0Gemfile
RubyGemsrspec~> 3.0Gemfile
RubyGemsrubocop~> 1.21Gemfile
RubyGemsrubocop-shopify~> 2.14Gemfile
RubyGemsrubocop-rake~> 0.6.0Gemfile
RubyGemsrubocop-sorbet~> 0.7Gemfile
RubyGemssorbet-staticGemfile
RubyGemstapioca~> 0.11Gemfile
RubyGemsdebugGemfile
RubyGemsirbGemfile
All dependencies 61

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

RegistryPackageVersionRelation
RubyGemsdebug1.11.1direct
RubyGemsirb1.17.0direct
RubyGemsrake13.3.1direct
RubyGemsrspec3.13.2direct
RubyGemsrubocop1.85.0direct
RubyGemsrubocop-rake0.6.0direct
RubyGemsrubocop-shopify2.18.0direct
RubyGemsrubocop-sorbet0.12.0direct
RubyGemssorbet-static0.6.12963direct
RubyGemstapioca0.17.10direct
RubyGemsaddressable2.8.8indirect
RubyGemsast2.4.3indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.0.1indirect
RubyGemsdate3.5.1indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemserb6.0.2indirect
RubyGemserubi1.13.1indirect
RubyGemsio-console0.8.2indirect
RubyGemsjson2.18.1indirect
RubyGemsjson-schema6.1.0indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmcp0.7.1indirect
RubyGemsnetrc0.11.0indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.10.2indirect
RubyGemspp0.6.3indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.3.1indirect
RubyGemspublic_suffix7.0.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrbi0.3.9indirect
RubyGemsrbs4.0.0.dev.5indirect
RubyGemsrdoc7.2.0indirect
RubyGemsregexp_parser2.11.3indirect
RubyGemsreline0.6.3indirect
RubyGemsrequire-hooks0.2.3indirect
RubyGemsrexml3.4.4indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.7indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop-ast1.49.0indirect
RubyGemsruby-lspindirect
RubyGemsruby-lsp0.26.7indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemssorbet0.6.12963indirect
RubyGemssorbet-runtime0.6.12963indirect
RubyGemssorbet-static-and-runtime0.6.12963indirect
RubyGemsspoom1.7.11indirect
RubyGemsstringio3.2.0indirect
RubyGemsthor1.5.0indirect
RubyGemstsort0.2.0indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsyard0.9.38indirect
RubyGemsyard-sorbet0.9.0indirect
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.15.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticsRubyGems.