Public record
Software health reportschema 0.14.0 · metrics 2.10.0 · 2026-07-18 21:39 UTC

calabash / calabash-ios-server

An embedded HTTP server for performing queries and test automation

Objective-CCustom license★ 86 stars⑂ 79 forkssince Jan 2012archivedView on GitHub ↗

calabash/calabash-ios-server holds a health index of 13 out of 100, placing it in the Critical band. It scores highest on Sustainability & Governance (60/100) and lowest on Vitality (18/100). The repository is archived, so no further maintenance is expected.

13
overall / 100
Critical

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.

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

Ownership

CalabashOrganization
30 followers34 public repossince Jan 2012

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

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 983 days ago
0/36Commit cadence0/52 weeks with commits
0/18Commit volume0 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject is archived
Inputs used
commits_last_year0
human_commit_share
days_since_last_push983
active_weeks_last_year0
How it's scored
27/27Ships releases2 releases published
0/36Release recencylatest release 1,740 days ago
12.6/27Release cadencea release every ~228.5 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count2
latest_release_tag0.23.0
releases_from_tagsno
days_since_latest_release1,740
mean_days_between_releases228.5
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?

59Moderate · 17% of overall
How it's scored
31.3/60Stars86 stars
15.8/25Forks79 forks
7/15Watchers19 watchers
Inputs used
forks79
stars86
watchers19
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
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
3.4/22.5Commit distributiontop contributor authored 85% of commits
13.5/13.5Contributor breadth34 contributors
10/10OpenSSF Scorecard: Contributorsproject has 11 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled34
top_contributor_share0.847
How it's scored
25.8/42Issue resolution62% of issues closed
27.5/30PR acceptance383/418 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
7.5/15OpenSSF Scorecard: Code-ReviewFound 11/20 approved changesets -- score normalized to 5
Inputs used
merged_prs383
open_issues25
closed_issues40
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.615
closed_unmerged_prs35
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
10.7/25Owner reach30 followers of calabash
23.2/25Track record34 public repos, account ~14 yr old
Inputs used
followers30
owner_typeOrganization
is_verified
owner_logincalabash
public_repos34
account_age_days5,301
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

30At Risk · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_site
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

23At Risk · 16% of overall
How it's scored
0/7.5Binary-Artifactsbinaries present in source code
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Tests0 out of 15 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
3.8/7.5Code-ReviewFound 11/20 approved changesets -- score normalized to 5
2.5/2.5Contributorsproject has 11 contributing companies or organizations
0/10Dangerous-Workflowno data
0/7.5Dependency-Update-Toolno update tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
0/7.5Maintainedproject is archived
0/5Packagingno data
0/5Pinned-Dependenciesno data
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-Permissionsno data
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate2.3
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Pinned-Dependencies, Signed-Releases, Token-Permissions. 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.

36Weak · 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
18/18One-command bootstrapMakefile
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-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_filesMakefile
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, OpenSSF Scorecard: Pinned-Dependencies. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeObjective-C without a type-check config
54.7/55Manageable file sizes4/673 source files over 60KB
Inputs used
primary_languageObjective-C
largest_source_bytes216,681
source_files_sampled673
oversized_source_files4

Key facts

86GitHub stars
34contributors
0commits, last 12 months
983days since last push
2releases
1bus factor
25open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 2.3 / 10
2.3aggregate

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-18 21:38 UTC

0Binary-Artifactsbinaries present in source code
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 15 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
5Code-ReviewFound 11/20 approved changesets -- score normalized to 5
10Contributorsproject has 11 contributing companies or organizations
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
0Maintainedproject is archived
n/aPackagingpackaging workflow not detected
n/aPinned-Dependenciesno dependencies found
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 17
RegistryPackageVersion constraintManifest
RubyGemsrun_loopGemfile
RubyGemsjson2.5.1Gemfile
RubyGemsluffaGemfile
RubyGemsrexmlGemfile
RubyGemsretriable2.0.2Gemfile
RubyGemsxcprettyGemfile
RubyGemsxamarin-test-cloudGemfile
RubyGemscalabash-cucumbercucumber/Gemfile
RubyGemscucumber7.0.0cucumber/Gemfile
RubyGemsrun_loopcucumber/Gemfile
RubyGemsjson2.5.1cucumber/Gemfile
RubyGemsrspec3.10.0cucumber/Gemfile
RubyGemsxamarin-test-cloud2.3.0cucumber/Gemfile
RubyGemsprycucumber/Gemfile
RubyGemspry-navcucumber/Gemfile
RubyGemsbriar2.0.5cucumber/Gemfile
RubyGemsluffacucumber/Gemfile
All dependencies 0

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

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

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