Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 15:21 UTC

opal / opal-rspec

Opal + RSpec = ♥️

RubyNo license detected★ 64 stars⑂ 15 forkssince Oct 2013View on GitHub ↗

opal/opal-rspec holds a health index of 41 out of 100, placing it in the Weak band. It scores highest on Sustainability & Governance (63/100) and lowest on Vitality (18/100). It was last updated 877 days ago. A single contributor accounts for most of its recent work.

41
overall / 100
Weak

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.

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

Ownership

OpalOrganization
35 followers26 public repossince Jun 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsopal-rspec1.0.0-371028 days ago

Metrics by category

Vitality

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

18Critical · 21% of overall
How it's scored
0/36Push recencylast push 877 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 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_year0
human_commit_share
days_since_last_push877
active_weeks_last_year0
How it's scored
27/27Ships releases8 releases published
0/36Release recencylatest release 1,334 days ago
12.6/27Release cadencea release every ~344.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count8
latest_release_tagv1.0.0
releases_from_tagsno
days_since_latest_release1,334
mean_days_between_releases344.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?

43Weak · 17% of overall
How it's scored
29.2/60Stars64 stars
9.6/25Forks15 forks
4.7/15Watchers8 watchers
Inputs used
forks15
stars64
watchers8
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
0/22.5Licenseno license file detected
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseno
readme_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
54.1/80Total downloads162,640 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesopal-rspec
dependents
ecosystemsrubygems
total_downloads162,640
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?

63Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
9.3/22.5Commit distributiontop contributor authored 59% of commits
8.1/13.5Contributor breadth6 contributors
10/10OpenSSF Scorecard: Contributorsproject has 14 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled6
top_contributor_share0.587
How it's scored
42/42Issue resolution100% of issues closed
19.4/30PR acceptance22/34 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 3/13 approved changesets -- score normalized to 2
Inputs used
merged_prs22
open_issues0
closed_issues61
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio1
closed_unmerged_prs12
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
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
11.2/25Owner reach35 followers of opal
22.4/25Track record26 public repos, account ~15 yr old
Inputs used
followers35
owner_typeOrganization
is_verified
owner_loginopal
public_repos26
account_age_days5,518
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
How it's scored
25/25Published & resolvable1 package(s) on rubygems
4/35Publish recencylatest publish 1,028 days ago
20/20Version history37 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesopal-rspec
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1,028

Engineering Quality

Are baseline engineering and documentation practices in place?

59Moderate · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 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 sitehttps://opalrb.com/docs/guides/master/rspec.html
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsopal-rspec, ruby, rspec, opal
has_wikiyes
homepagehttps://opalrb.com/docs/guides/master/rspec.html
docs_sitehttps://opalrb.com/docs/guides/master/rspec.html
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

34At Risk · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
0/2.5CI-Tests0 out of 6 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 3/13 approved changesets -- score normalized to 2
2.5/2.5Contributorsproject has 14 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
0/2.5Licenselicense file not 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
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate3.4
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.

34At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
0/40Legible commit historyno data
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share
agent_instruction_files
agent_instruction_max_bytes
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
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
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
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
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
54/55Manageable file sizes3/160 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes100,892
source_files_sampled160
oversized_source_files3
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 examplesexample
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

64GitHub stars
6contributors
0commits, last 12 months
877days since last push
8releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

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-07-20 15:21 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
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 3/13 approved changesets -- score normalized to 2
10Contributorsproject has 14 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
0Licenselicense file not 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 17
RegistryPackageVersion constraintManifest
RubyGemsrspecGemfile
RubyGemsrspec-supportGemfile
RubyGemsrspec-coreGemfile
RubyGemsrspec-mocksGemfile
RubyGemsrspec-expectationsGemfile
RubyGemspryGemfile
RubyGemsopalGemfile
RubyGemsopalGemfile
RubyGemsopalGemfile
RubyGemsopal-sprockets>=1.0Gemfile
RubyGemspumaGemfile
RubyGemsrack<3Gemfile
RubyGemsbase64Gemfile
RubyGemsrakeexample/Gemfile
RubyGemsopal-rspecexample/Gemfile
RubyGemsopalexample/Gemfile
RubyGemsopal-sprocketsexample/Gemfile
All dependencies 19

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

RegistryPackageVersionRelation
RubyGemsbase64direct
RubyGemsopaldirect
RubyGemsopal-rspecdirect
RubyGemsopal-sprocketsdirect
RubyGemsprydirect
RubyGemspumadirect
RubyGemsrackdirect
RubyGemsrakedirect
RubyGemsrspecdirect
RubyGemsrspec-coredirect
RubyGemsrspec-expectationsdirect
RubyGemsrspec-mocksdirect
RubyGemsrspec-supportdirect
RubyGemsapparitionindirect
RubyGemsappraisalindirect
RubyGemsbundlerindirect
RubyGemscapybaraindirect
RubyGemslaunchyindirect
RubyGemsyardindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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.16.0 — full methodology · metrics wiki.

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