Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-27 22:35 UTC

sidekiq / sidekiq

Simple, efficient background processing for Ruby

RubyCustom license★ 13,553 stars⑂ 2,478 forkssince Jan 2012View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

sidekiq/sidekiq holds a health index of 92 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (92/100) and lowest on AI Readiness (45/100). It was last updated 10 days ago. A single contributor accounts for most of its recent work.

92
overall / 100
Excellent

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.

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

Ownership

SidekiqOrganization
59 followers2 public repossince Feb 2023

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemssidekiq8.1.7-24210 days ago

Metrics by category

Vitality

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

89Excellent · 21% of overall
How it's scored
28.8/36Push recencylast push 10 days ago
32.5/36Commit cadence47/52 weeks with commits
18/18Commit volume274 commits in the last year
10/10OpenSSF Scorecard: Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year274
human_commit_share0.98
days_since_last_push10
active_weeks_last_year47
How it's scored
16.2/27Ships releases95 version tags (no GitHub releases)
36/36Release recencylatest release 10 days ago
27/27Release cadencea release every ~31.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count95
latest_release_tagv8.1.7
releases_from_tagsyes
days_since_latest_release10
mean_days_between_releases31.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?

92Excellent · 17% of overall
How it's scored
60/60Stars13,553 stars
25/25Forks2,478 forks
12.8/15Watchers203 watchers
Inputs used
forks2,478
stars13,553
watchers203
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
16.9/22.5Licenselicense file present, not a recognized license
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateno
How it's scored
80/80Total downloads332,707,622 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagessidekiq
dependents
ecosystemsrubygems
total_downloads332,707,622
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 breadth99 contributors
10/10OpenSSF Scorecard: Contributorsproject has 53 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.784
How it's scored
41.8/42Issue resolution100% of issues closed
22/30PR acceptance1,357/1,850 decided PRs merged
6.5/13Newcomer PR acceptance1/2 first-time contributors' PRs merged in 30d
9/15OpenSSF Scorecard: Code-ReviewFound 20/29 approved changesets -- score normalized to 6
Inputs used
merged_prs1,357
open_issues18
closed_issues4,924
prs_merged_7d0
prs_decided_7d1
prs_merged_30d2
prs_decided_30d3
issue_closed_ratio0.996
closed_unmerged_prs493
first_time_authors_30d2
first_time_prs_merged_30d1
first_time_prs_decided_30d2
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
12.8/25Owner reach59 followers of sidekiq
10.6/25Track record2 public repos, account ~3 yr old
Inputs used
followers59
owner_typeOrganization
is_verifiedno
owner_loginsidekiq
public_repos2
account_age_days1,297

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

80Excellent · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
18/20OpenSSF Scorecard: CI-Tests19 out of 21 merged PRs checked by a CI test -- score normalized to 9
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttps://sidekiq.org
10/10Repository description
10/10Topics4 topics
10/10Wiki
Inputs used
topicsruby, sidekiq, background-jobs, jobs
has_wikiyes
homepagehttps://sidekiq.org
docs_sitehttps://sidekiq.org
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

75Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.2/2.5CI-Tests19 out of 21 merged PRs checked by a CI test -- score normalized to 9
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4.5/7.5Code-ReviewFound 20/29 approved changesets -- score normalized to 6
2.5/2.5Contributorsproject has 53 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.2/2.5Licenselicense file detected
7.5/7.5Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
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
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_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate7.5
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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
31.6/40Legible commit history58 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.592
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
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
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_share0
toolchain_manifests
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codeRuby without a type-check config
54.7/55Manageable file sizes1/177 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes199,560
source_files_sampled177
oversized_source_files1
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

13,553GitHub stars
99contributors
274commits, last 12 months
10days since last push
95releases
1bus factor
18open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem

More detail

Star and fork history 0 ★ / 2,478 ⇿
0Stars
2,478Forks
87Releases

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.

1,0001,5002,0002,5002,478142019-072023-022026-08
Major 3Minor 9Patch 75

Each point covers 7 days.

OpenSSF Scorecard 7.5 / 10
7.5aggregate

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-27 22:35 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
9CI-Tests19 out of 21 merged PRs checked by a CI test -- score normalized to 9
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
6Code-ReviewFound 20/29 approved changesets -- score normalized to 6
10Contributorsproject has 53 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 commit(s) and 18 issue activity found in the last 90 days -- score normalized to 10
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
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 19
RegistryPackageVersion constraintManifest
RubyGemsredis-clientGemfile
RubyGemsvernierGemfile
RubyGemsratatui_rubyGemfile
RubyGemssidekiqbare/Gemfile
RubyGemsactionmailermyapp/Gemfile
RubyGemsactionpackmyapp/Gemfile
RubyGemsactivejobmyapp/Gemfile
RubyGemsactiverecordmyapp/Gemfile
RubyGemsrailtiesmyapp/Gemfile
RubyGemspumamyapp/Gemfile
RubyGemssidekiqmyapp/Gemfile
RubyGemssqlite3~> 2.2myapp/Gemfile
RubyGemsjsonmyapp/Gemfile
RubyGemsratatui_rubymyapp/Gemfile
RubyGemsafter_commit_everywheremyapp/Gemfile
RubyGemssidekiq-redis_infomyapp/Gemfile
RubyGemsverniermyapp/Gemfile
RubyGemsdebugmyapp/Gemfile
RubyGemsmsgpackmyapp/Gemfile
All dependencies 22

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

RegistryPackageVersionRelation
RubyGemsafter_commit_everywheredirect
RubyGemsdebugdirect
RubyGemsjsondirect
RubyGemsmsgpackdirect
RubyGemspumadirect
RubyGemsratatui_rubydirect
RubyGemsredis-clientdirect
RubyGemssidekiqdirect
RubyGemssidekiq-redis_infodirect
RubyGemssqlite3direct
RubyGemsvernierdirect
RubyGemsactiverecord-jdbcsqlite3-adapterindirect
RubyGemsconnection_poolindirect
RubyGemscsvindirect
RubyGemsherbindirect
RubyGemsloggerindirect
RubyGemsminitestindirect
RubyGemsrackindirect
RubyGemsruby-profindirect
RubyGemssimplecovindirect
RubyGemsstandardindirect
RubyGemstoxiproxyindirect
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.34.0 — full methodology · metrics wiki.

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