Public record
Software health reportschema 0.27.0 · metrics 2.5.0 · 2026-07-26 19:24 UTC

ccutrer / waterfurnace_aurora

Library for communication with WaterFurnace Aurora control systems

RubyMIT★ 62 stars⑂ 15 forkssince Jun 2020View on GitHub ↗

ccutrer/waterfurnace_aurora holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Engineering Quality (72/100) and lowest on AI Readiness (26/100). It was last updated today. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

Cody CutrerPersonal account
87 followers181 public repossince Jan 2010@instructure

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
RubyGemswaterfurnace_aurora1.7.0-790 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
4.8/36Commit cadence — 7/52 weeks with commits
13.4/18Commit volume — 30 commits in the last year
1/10OpenSSF Scorecard: Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
Inputs used
commits_last_year30
human_commit_share0.81
days_since_last_push0
active_weeks_last_year7
How it's scored
16.2/27Ships releases — 74 version tags (no GitHub releases)
36/36Release recency — latest release 0 days ago
19.8/27Release cadence — a release every ~60.2 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count74
latest_release_tagv1.7.0
releases_from_tagsyes
days_since_latest_release0
mean_days_between_releases60.2
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
29/60Stars — 62 stars
9.6/25Forks — 15 forks
5.8/15Watchers — 12 watchers
Inputs used
forks15
stars62
watchers12
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
51.8/80Total downloads — 95,981 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packageswaterfurnace_aurora
dependents
ecosystemsrubygems
total_downloads95,981
monthly_downloads
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 factor — 1 contributor(s) cover half of all commits
0.7/22.5Commit distribution — top contributor authored 97% of commits
4.1/13.5Contributor breadth — 3 contributors
10/10OpenSSF Scorecard: Contributors — project has 3 contributing companies or organizations -- score normalized to 10
Inputs used
bus_factor1
contributors_sampled3
top_contributor_share0.971
How it's scored
37.8/42Issue resolution — 90% of issues closed
20.6/30PR acceptance — 24/35 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/23 approved changesets -- score normalized to 0
Inputs used
merged_prs24
open_issues7
closed_issues64
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.901
closed_unmerged_prs11
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
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14/25Owner reach — 87 followers of ccutrer
25/25Track record — 181 public repos, account ~16 yr old
Inputs used
followers87
owner_typeUser
is_verified
owner_loginccutrer
public_repos181
account_age_days6,023
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 — 79 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packageswaterfurnace_aurora
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

72Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
0/24Tests present
16/16Linter config — .rubocop.yml
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 8 out of 8 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsno
has_editorconfigno
has_linter_configyes
has_precommit_configyes
How it's scored
30/30README
25/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

55Moderate · 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 — 8 out of 8 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 1/23 approved changesets -- score normalized to 0
2.5/2.5Contributors — project has 3 contributing companies or organizations -- score normalized to 10
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.8/7.5Maintained — 2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
5/5Packaging — packaging workflow detected
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
4.5/7.5Vulnerabilities — 4 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated17
scorecard_versionv5.5.0
checks_inconclusive1
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): 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
advisories4
affected_packages3
assessed_packages68
unassessed_packages9
affected_by_severityhigh 2, 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 68 resolved dependencies against OSV. 9 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.

26At Risk · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
6.6/40Legible commit history — 10 of 81 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
legible_history_share0.123
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
0/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — Dockerfile, lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
8/8Automated maintenance — 19 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_testsno
lockfilesGemfile.lock
has_dockerfileyes
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.19
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/20 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes34,064
source_files_sampled20
oversized_source_files0

Key facts

62GitHub stars
3contributors
30commits, last 12 months
0days since last push
74releases
1bus factor
7open 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 ★ / 15 ⇿
0Stars
15Forks
48Releases

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.

03581013151522021-092023-112026-01
Major 1Minor 8Patch 39

Each point covers 4 days.

OpenSSF Scorecard 4.4 / 10
4.4aggregate

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-26 19:24 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests8 out of 8 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 1/23 approved changesets -- score normalized to 0
10Contributorsproject has 3 contributing companies or organizations -- score normalized to 10
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
1Maintained2 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 1
10Packagingpackaging workflow 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
6Vulnerabilities4 existing vulnerabilities detected
Direct dependencies 6
RegistryPackageVersion constraintManifest
RubyGemsdebug~> 1.9Gemfile
RubyGemsesphome~> 1.1Gemfile
RubyGemspycall~> 1.5Gemfile
RubyGemsrake~> 13.3Gemfile
RubyGemsrubocop-inst~> 1.0Gemfile
RubyGemsrubocop-rake~> 0.6Gemfile
All dependencies 77

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

RegistryPackageVersionRelation
RubyGemsdebug1.11.1direct
RubyGemsesphome1.1.0direct
RubyGemspycall1.5.2direct
RubyGemsrake13.3.1direct
RubyGemsrubocop-inst1.2.3direct
RubyGemsrubocop-rake0.7.1direct
RubyGemsast2.4.3indirect
RubyGemsbase640.3.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsccutrer-serialportindirect
RubyGemsccutrer-serialport1.1.0indirect
RubyGemscurses1.6.0indirect
RubyGemsdate3.5.1indirect
RubyGemsdigest-crc0.7.0indirect
RubyGemsecdsa1.2.0indirect
RubyGemsed4480.1.2indirect
RubyGemserb6.0.1indirect
RubyGemsffi1.17.3indirect
RubyGemsgoogle-protobuf4.35.1indirect
RubyGemshomie-mqttindirect
RubyGemshomie-mqtt1.8.2indirect
RubyGemshttp-21.2.1indirect
RubyGemshttpx1.8.1indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.17.0indirect
RubyGemsjson2.19.2indirect
RubyGemslanguage_server-protocol3.17.0.5indirect
RubyGemslint_roller1.1.0indirect
RubyGemslogger1.7.0indirect
RubyGemsmqtt-ccutrer1.1.1indirect
RubyGemsmqtt-homeassistant1.2.0indirect
RubyGemsmqtt-homie-homeassistantindirect
RubyGemsmqtt-homie-homeassistant1.2.2indirect
RubyGemsmustermann3.0.4indirect
RubyGemsnet-telnet0.2.0indirect
RubyGemsnet-telnet-rfc2217indirect
RubyGemsnet-telnet-rfc22171.0.2indirect
RubyGemsnio4r2.7.5indirect
RubyGemsnoise-ruby0.10.1indirect
RubyGemsparallel1.27.0indirect
RubyGemsparser3.3.10.1indirect
RubyGemspp0.6.3indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemspsych5.3.1indirect
RubyGemspumaindirect
RubyGemspuma7.2.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.6indirect
RubyGemsrack-protection4.2.1indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrackupindirect
RubyGemsrackup2.3.1indirect
RubyGemsrainbow3.1.1indirect
RubyGemsrbnacl7.1.2indirect
RubyGemsrdoc7.2.0indirect
RubyGemsregexp_parser2.11.3indirect
RubyGemsreline0.6.3indirect
RubyGemsrmodbusindirect
RubyGemsrmodbus2.1.3indirect
RubyGemsrubocop1.84.1indirect
RubyGemsrubocop-ast1.49.0indirect
RubyGemsrubocop-performance1.26.1indirect
RubyGemsruby-hmac0.4.0indirect
RubyGemsruby-progressbar1.13.0indirect
RubyGemsruby2_keywords0.0.5indirect
RubyGemssinatraindirect
RubyGemssinatra4.2.1indirect
RubyGemsstringio3.2.0indirect
RubyGemstilt2.7.0indirect
RubyGemstsort0.2.0indirect
RubyGemsunicode-display_width3.2.0indirect
RubyGemsunicode-emoji4.2.0indirect
RubyGemsuriindirect
RubyGemsuri1.1.1indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
Dependency advisories 3

This repository publishes no package the index resolves, so its own dependency graph was assessed — 68 packages, which also include development and test pins that never ship: 3 carry known advisories, of which 0 are direct. 9 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
erb6.0.1indirecthigh16.0.4
puma7.2.0indirecthigh28.0.2
json2.19.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

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.5.0, schema v0.27.0 — full methodology · metrics wiki.

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