Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-11 01:09 UTC

0exp / redis_queued_locks

Distributed locks with "prioritized lock acquisition queue" capabilities based on the Redis Database. Provides flexible invocation flow, parametrized time limits, zombie locks elimination, instrumentation, logging, etc.

RubyMIT★ 52 stars⑂ 1 forksince Feb 2024View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

0exp/redis_queued_locks holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (80/100) and lowest on Sustainability & Governance (49/100). It was last updated today. A single contributor accounts for most of its recent work.

67
overall / 100
Good

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.

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

Ownership

Rustam IbragimovPersonal account
139 followers133 public repossince Oct 2017@umbrellio @cado-labs @smart-rb

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
RubyGemsredis_queued_locks1.18.0-640 days ago

Metrics by category

Vitality

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

72Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
8.3/36Commit cadence — 12/52 weeks with commits
15.1/18Commit volume — 47 commits in the last year
8/10OpenSSF Scorecard: Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year47
human_commit_share1
days_since_last_push0
active_weeks_last_year12
How it's scored
16.2/27Ships releases — 66 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~82.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count66
latest_release_tagv1.18.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases82.8
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?

51Moderate · 17% of overall
How it's scored
27.7/60Stars — 52 stars
0/25Forks — 1 forks
0/15Watchers — 2 watchers
Inputs used
forks1
stars52
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized 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_badges5
has_contributingno
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
54.8/80Total downloads — 188,212 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesredis_queued_locks
dependents—
ecosystemsrubygems
total_downloads188,212
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?

49Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
10/10OpenSSF Scorecard: Contributors — project has 4 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.998
How it's scored
0/42Issue resolution — 0% of issues closed
23.6/30PR acceptance — 11/14 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs11
open_issues2
closed_issues0
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0
closed_unmerged_prs3
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
15.4/25Owner reach — 139 followers of 0exp
25/25Track record — 133 public repos, account ~8 yr old
Inputs used
followers139
owner_typeUser
is_verified—
owner_login0exp
public_repos133
account_age_days3,269
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
35/35Publish recency — latest publish 0 days ago
20/20Version history — 64 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesredis_queued_locks
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — https://github.com/0exp/redis_queued_locks
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicsredis-lock, redlock, advisory-lock, queued-lock, distributed-lock, distributed-redis-lock, redis-queued-lock, distributed-locks, distributed-redis-locks, redis-locks, redis-queued-locks, redlock-ruby, reentrant-locks, reentrant-redis-lock, rql, ruby
has_wikiyes
homepagehttps://github.com/0exp/redis_queued_locks
docs_sitehttps://github.com/0exp/redis_queued_locks
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

54Moderate · 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
2.5/2.5CI-Tests — 2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 4 contributing companies or organizations
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
6/7.5Maintained — 10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
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_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages67
unassessed_packages1
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 67 resolved dependencies against OSV. 1 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.

54Moderate · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://redis.io/llms.txt)
2.1/40Legible commit history — 4 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://redis.io/llms.txt
legible_history_share0.04
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes5,158
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — lockfile
4/10Demonstrated agent practice — 2 of the last 100 commits agent-authored or agent-credited
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_configyes
typecheck_configs—
agent_commit_share0.02
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
54.1/55Manageable file sizes — 1/60 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes142,893
source_files_sampled60
oversized_source_files1

Key facts

52GitHub stars
2contributors
47commits, last 12 months
0days since last push
66releases
1bus factor
2open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

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-10-11 01:09 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests2 out of 2 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 4 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained10 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 8
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 13
RegistryPackageVersion constraintManifest
RubyGemsactivesupport—Gemfile
RubyGemsarmitage-rubocop—Gemfile
RubyGemsbundler—Gemfile
RubyGemspry—Gemfile
RubyGemspry-doc—Gemfile
RubyGemsrake—Gemfile
RubyGemsrbs—Gemfile
RubyGemstsort—Gemfile
RubyGemsreline—Gemfile
RubyGemsrspec—Gemfile
RubyGemsrspec-retry—Gemfile
RubyGemssimplecov—Gemfile
RubyGemssteep—Gemfile
All dependencies 68

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

RegistryPackageVersionRelation
RubyGemsactivesupport8.1.4direct
RubyGemsarmitage-rubocop1.91.0.0direct
RubyGemspry0.16.0direct
RubyGemspry-doc1.7.0direct
RubyGemsrake13.4.2direct
RubyGemsrbs4.2.0direct
RubyGemsreline0.7.0direct
RubyGemsrspec3.13.2direct
RubyGemsrspec-retry0.6.2direct
RubyGemssimplecov1.3.2direct
RubyGemssteep2.1.0direct
RubyGemstsort0.2.0direct
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.3indirect
RubyGemscoderay1.1.3indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscsv3.3.6indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsdrb2.2.3indirect
RubyGemsffi1.17.4indirect
RubyGemsfileutils1.8.1indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.9.4indirect
RubyGemsjson3.0.2indirect
RubyGemslanguage_server-protocol3.17.0.6indirect
RubyGemslint_roller1.1.0indirect
RubyGemslisten3.10.1indirect
RubyGemslogger1.7.0indirect
RubyGemsmethod_source1.1.0indirect
RubyGemsminitest6.0.6indirect
RubyGemsparallel2.3.0indirect
RubyGemsparser3.3.12.0indirect
RubyGemsprism1.9.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.7indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrb-fsevent0.11.2indirect
RubyGemsrb-inotify0.11.1indirect
RubyGemsredis-client—indirect
RubyGemsredis-client0.31.0indirect
RubyGemsregexp_parser2.13.1indirect
RubyGemsrspec-core3.13.6indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.8indirect
RubyGemsrspec-support3.13.7indirect
RubyGemsrubocop1.91.0indirect
RubyGemsrubocop-ast1.50.0indirect
RubyGemsrubocop-capybara3.0.0indirect
RubyGemsrubocop-factory_bot2.28.0indirect
RubyGemsrubocop-on-rbs2.2.0indirect
RubyGemsrubocop-performance1.27.0indirect
RubyGemsrubocop-rails2.38.0indirect
RubyGemsrubocop-rake0.7.1indirect
RubyGemsrubocop-rspec3.10.2indirect
RubyGemsrubocop-rspec_rails2.32.0indirect
RubyGemsrubocop-thread_safety0.8.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsrubydex0.4.1indirect
RubyGemssecurerandom0.4.1indirect
RubyGemsstrscan3.1.8indirect
RubyGemsterminal-table4.0.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsunicode-display_width3.3.0indirect
RubyGemsunicode-emoji4.3.0indirect
RubyGemsuri1.1.2indirect
RubyGemsyard0.9.45indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 67 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct. 1 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 statistics — RubyGems.