Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 06:27 UTC

loops-so / loops-rb

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

loops-so/loops-rb holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Engineering Quality (72/100) and lowest on AI Readiness (41/100). It was last updated 12 days ago. 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

LoopsOrganization
20 followers16 public repossince Oct 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsloops_sdk2.4.0-1242 days ago

Metrics by category

Vitality

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

71Good · 21% of overall
How it's scored
28.8/36Push recencylast push 12 days ago
6.2/36Commit cadence9/52 weeks with commits
11.9/18Commit volume20 commits in the last year
10/10OpenSSF Scorecard: Maintained14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year20
human_commit_share0.982
days_since_last_push12
active_weeks_last_year9
How it's scored
27/27Ships releases13 releases published
36/36Release recencylatest release 12 days ago
19.8/27Release cadencea release every ~74.9 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count13
latest_release_tagv2.5.0
releases_from_tagsno
days_since_latest_release12
mean_days_between_releases74.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?

51Moderate · 17% of overall
How it's scored
7.7/60Stars4 stars
0/25Forks1 forks
0/15Watchers0 watchers
Inputs used
forks1
stars4
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

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_badges1
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesshields.io
has_pull_request_templateyes
How it's scored
49.8/80Total downloads62,594 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesloops_sdk
dependents
ecosystemsrubygems
total_downloads62,594
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?

59Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0.4/22.5Commit distributiontop contributor authored 98% of commits
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.982
How it's scored
42/42Issue resolution100% of issues closed
26.2/30PR acceptance7/8 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
3/15OpenSSF Scorecard: Code-ReviewFound 5/18 approved changesets -- score normalized to 2
Inputs used
merged_prs7
open_issues0
closed_issues1
prs_merged_7d0
prs_decided_7d0
prs_merged_30d1
prs_decided_30d2
issue_closed_ratio1
closed_unmerged_prs1
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
9.5/25Owner reach20 followers of loops-so
18.7/25Track record16 public repos, account ~4 yr old
Inputs used
followers20
owner_typeOrganization
is_verifiedno
owner_loginloops-so
public_repos16
account_age_days1,784

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter config.rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests5 out of 5 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

Documentation

55Moderate
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://loops.so/docs/api-reference
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://loops.so/docs/api-reference
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
2.5/2.5CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1.5/7.5Code-ReviewFound 5/18 approved changesets -- score normalized to 2
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
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
7.5/7.5Maintained14 commit(s) and 0 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
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_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.5
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 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
advisories7
affected_packages5
assessed_packages36
unassessed_packages1
affected_by_severityhigh 3, moderate 1, low 1
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 36 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.

41Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
15/15Machine-readable docs (llms.txt)llms.txt served by the project website (https://loops.so/llms.txt)
6.8/40Legible commit history7 of 55 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://loops.so/llms.txt
legible_history_share0.127
agent_instruction_files
agent_instruction_max_bytes
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 agent-authored commits among the last 56
8/8Automated maintenance1 of the last 56 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
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.018
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/36 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes20,796
source_files_sampled36
oversized_source_files0

Key facts

4GitHub stars
2contributors
20commits, last 12 months
12days since last push
13releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

OpenSSF Scorecard 4.5 / 10
4.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-09-16 06:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests5 out of 5 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2Code-ReviewFound 5/18 approved changesets -- score normalized to 2
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 0 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
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 2
RegistryPackageVersion constraintManifest
RubyGemsrake~> 13.0Gemfile
RubyGemsrubocop~> 1.21Gemfile
All dependencies 37

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

RegistryPackageVersionRelation
RubyGemsrake13.3.0direct
RubyGemsrubocop1.80.0direct
RubyGemsaddressable2.8.7indirect
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal3.2.2indirect
RubyGemscrack1.0.0indirect
RubyGemsdiff-lcs1.6.2indirect
RubyGemsfaradayindirect
RubyGemsfaraday2.13.4indirect
RubyGemsfaraday-net_http3.4.1indirect
RubyGemshashdiff1.2.0indirect
RubyGemsjson2.13.2indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsnet-http0.6.0indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.9.0indirect
RubyGemsprism1.4.0indirect
RubyGemspublic_suffix6.0.2indirect
RubyGemsracc1.8.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsregexp_parser2.11.2indirect
RubyGemsrexml3.4.1indirect
RubyGemsrspec3.13.1indirect
RubyGemsrspec-core3.13.5indirect
RubyGemsrspec-expectations3.13.5indirect
RubyGemsrspec-mocks3.13.5indirect
RubyGemsrspec-support3.13.5indirect
RubyGemsrubocop-ast1.46.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsunicode-display_width3.1.5indirect
RubyGemsunicode-emoji4.0.4indirect
RubyGemsuri1.0.3indirect
RubyGemsvcr6.3.1indirect
RubyGemswebmock3.25.1indirect
Dependency advisories 5

This repository publishes no package the index resolves, so its own dependency graph was assessed — 36 packages, which also include development and test pins that never ship: 5 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.

PackageVersionRelationSeverityAdvisoriesFixed in
addressable2.8.7indirecthigh12.9.0
faraday2.13.4indirecthigh32.14.3
uri1.0.3indirecthigh11.0.4
rexml3.4.1indirectmoderate13.4.2
json2.13.2indirectlow12.19.9

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.