Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-10 07:52 UTC

CocoaPods / CLAide

A small command-line interface framework.

RubyMIT★ 199 stars⑂ 31 forkssince Oct 2012View on GitHub ↗

CocoaPods/CLAide holds a health index of 32 out of 100, placing it in the At Risk band. It scores highest on Sustainability & Governance (70/100) and lowest on Vitality (18/100). It was last updated 945 days ago. 2 contributors account for most of its recent work.

32
overall / 100
At Risk

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.

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

Ownership

CocoaPodsOrganization
364 followers70 public repossince Nov 2011

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
RubyGemsclaide1.1.0-251701 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 recency — last push 945 days ago
0/36Commit cadence — 0/52 weeks with commits
0/18Commit volume — 0 commits in the last year
0/10OpenSSF Scorecard: Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
Inputs used
commits_last_year0
human_commit_share0.96
days_since_last_push945
active_weeks_last_year0
How it's scored
27/27Ships releases — 19 releases published
0/36Release recency — latest release 1,656 days ago
12.6/27Release cadence — a release every ~269.8 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count19
latest_release_tag1.1.0
releases_from_tagsno
days_since_latest_release1,656
mean_days_between_releases269.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?

65Good · 17% of overall
How it's scored
37.3/60Stars — 199 stars
12.3/25Forks — 31 forks
6.7/15Watchers — 17 watchers
Inputs used
forks31
stars199
watchers17
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
80/80Total downloads — 251,225,136 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesclaide
dependents—
ecosystemsrubygems
total_downloads251,225,136
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?

70Good · 23% of overall
How it's scored
25.2/54Bus factor — 2 contributor(s) cover half of all commits
13.6/22.5Commit distribution — top contributor authored 39% of commits
13.5/13.5Contributor breadth — 18 contributors
10/10OpenSSF Scorecard: Contributors — project has 53 contributing companies or organizations
Inputs used
bus_factor2
contributors_sampled18
top_contributor_share0.394
How it's scored
42/42Issue resolution — 100% of issues closed
20.8/30PR acceptance — 36/52 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
6/15OpenSSF Scorecard: Code-Review — Found 6/14 approved changesets -- score normalized to 4
Inputs used
merged_prs36
open_issues0
closed_issues45
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs16
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 backing — organization-owned
0/20Verified domain
18.4/25Owner reach — 364 followers of CocoaPods
25/25Track record — 70 public repos, account ~14 yr old
Inputs used
followers364
owner_typeOrganization
is_verifiedno
owner_loginCocoaPods
public_repos70
account_age_days5,416
How it's scored
25/25Published & resolvable — 1 package(s) on rubygems
4/35Publish recency — latest publish 1,701 days ago
20/20Version history — 25 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesclaide
ecosystemsrubygems
any_deprecatedno
min_days_since_publish1,701

Engineering Quality

Are baseline engineering and documentation practices in place?

64Moderate · 19% of overall
How it's scored
24/24CI workflows — 1 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
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 — http://rubydoc.info/gems/claide
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttp://rubydoc.info/gems/claide
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

44Weak · 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
0/2.5CI-Tests — 0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 6/14 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 53 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
0/7.5Maintained — 0 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 0
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
2.2/7.5Vulnerabilities — 7 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate3.8
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.
How it's scored
17.1/35Direct dependencies free of known advisories — 1 affected: rake 10.3.2 (moderate 6.4)
0/25Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope
34.5/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 2,385 days ago
Inputs used
sourceosv
advisories7
affected_packages2
assessed_packages29
unassessed_packages0
affected_by_severityhigh 1, moderate 1
direct_affected_packages1
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories. Remaining weights renormalized. Matched 29 resolved dependencies against OSV. 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.

48Weak · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14.4/40Legible commit history — 26 of 96 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.271
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 environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 4 of the last 100 commits are automated dependency updates
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
toolchain_manifests—
dependency_bot_commit_share0.04
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/34 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes20,696
source_files_sampled34
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
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

199GitHub stars
18contributors
0commits, last 12 months
945days since last push
19releases
2bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 31 ⇿
0Stars
31Forks
19Releases

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.

01325383122013-092018-122024-03
Major 1Minor 7Patch 7

Each point covers 10 days.

OpenSSF Scorecard 3.8 / 10
3.8aggregate

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-10 07:52 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 9 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 6/14 approved changesets -- score normalized to 4
10Contributorsproject has 53 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 9
RegistryPackageVersion constraintManifest
RubyGemsrake—Gemfile
RubyGemsbacon—Gemfile
RubyGemsjson< 3Gemfile
RubyGemsmocha-on-bacon—Gemfile
RubyGemsprettybacon—Gemfile
RubyGemsparallel<= 1.19.2Gemfile
RubyGemsrubocop<= 0.81.0Gemfile
RubyGemsrubocop-performance<= 1.5.2Gemfile
RubyGemssimplecov—Gemfile
All dependencies 29

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

RegistryPackageVersionRelation
RubyGemsbacon1.2.0direct
RubyGemsjson2.5.1direct
RubyGemsmocha-on-bacon0.2.2direct
RubyGemsparallel1.19.2direct
RubyGemsprettybacon0.0.2direct
RubyGemsrake10.3.2direct
RubyGemsrubocop0.81.0direct
RubyGemsrubocop-performance1.5.2direct
RubyGemssimplecov0.9.1direct
RubyGemsast2.4.2indirect
RubyGemscolored1.2indirect
RubyGemsdocile1.1.5indirect
RubyGemsffi1.14.2indirect
RubyGemsjaro_winkler1.5.4indirect
RubyGemskicker3.0.0indirect
RubyGemslisten1.3.1indirect
RubyGemsmetaclass0.0.4indirect
RubyGemsmocha1.1.0indirect
RubyGemsmulti_json1.10.1indirect
RubyGemsnotify0.5.2indirect
RubyGemsparser3.1.0.0indirect
RubyGemsrainbow3.0.0indirect
RubyGemsrb-fsevent0.9.4indirect
RubyGemsrb-inotify0.9.5indirect
RubyGemsrb-kqueue0.2.3indirect
RubyGemsrexml3.2.5indirect
RubyGemsruby-progressbar1.11.0indirect
RubyGemssimplecov-html0.8.0indirect
RubyGemsunicode-display_width1.8.0indirect
Dependency advisories 2

This repository publishes no package the index resolves, so its own dependency graph was assessed — 29 packages, which also include development and test pins that never ship: 2 carry known advisories, of which 1 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
rexml3.2.5indirecthigh63.3.9
rake10.3.2directmoderate112.3.3

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.