Public record
Software health reportschema 0.15.0 · metrics 2.10.0 · 2026-07-20 14:28 UTC

daddyz / phonelib

Ruby gem for phone validation and formatting using google libphonenumber library data

RubyMIT★ 1,162 stars⑂ 138 forkssince Oct 2012View on GitHub ↗

daddyz/phonelib holds a health index of 62 out of 100, placing it in the Moderate band. It scores highest on Community & Adoption (72/100) and lowest on AI Readiness (31/100). It was last updated 38 days ago. A single contributor accounts for most of its recent work.

62
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.

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

Ownership

Vadim SenderovichPersonal account
13 followers21 public repossince Jan 2012

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
RubyGemsphonelib0.10.22-14238 days ago

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
18/36Push recencylast push 38 days ago
9.7/36Commit cadence14/52 weeks with commits
13.9/18Commit volume34 commits in the last year
8/10OpenSSF Scorecard: Maintained8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8
Inputs used
commits_last_year34
human_commit_share
days_since_last_push38
active_weeks_last_year14

Release discipline

100Exceptional
How it's scored
27/27Ships releases84 releases published
36/36Release recencylatest release 38 days ago
27/27Release cadencea release every ~30 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count84
latest_release_tagv0.10.22
releases_from_tagsno
days_since_latest_release38
mean_days_between_releases30
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?

72Good · 17% of overall
How it's scored
49.7/60Stars1,162 stars
17.8/25Forks138 forks
6.2/15Watchers14 watchers
Inputs used
forks138
stars1,162
watchers14
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized 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
80/80Total downloads75,764,284 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesphonelib
dependents
ecosystemsrubygems
total_downloads75,764,284
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?

60Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
4.1/22.5Commit distributiontop contributor authored 82% of commits
13.5/13.5Contributor breadth54 contributors
6/10OpenSSF Scorecard: Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
Inputs used
bus_factor1
contributors_sampled54
top_contributor_share0.818
How it's scored
40.4/42Issue resolution96% of issues closed
20.1/30PR acceptance83/124 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-ReviewFound 3/27 approved changesets -- score normalized to 1
Inputs used
merged_prs83
open_issues9
closed_issues220
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.961
closed_unmerged_prs41
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
8.2/25Owner reach13 followers of daddyz
21.8/25Track record21 public repos, account ~14 yr old
Inputs used
followers13
owner_typeUser
is_verified
owner_logindaddyz
public_repos21
account_age_days5,292
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

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

Engineering Quality

Are baseline engineering and documentation practices in place?

50Moderate · 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
20/20OpenSSF Scorecard: CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics6 topics
10/10Wiki
Inputs used
topicsruby, google-libphonenumber, phone-validation, phone-parse, phone-number, parsing
has_wikiyes
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?

40Weak · 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-Tests3 out of 3 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
0.8/7.5Code-ReviewFound 3/27 approved changesets -- score normalized to 1
1.5/2.5Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
0/10Dangerous-Workflowno data
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
6/7.5Maintained8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8
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
0/7.5Vulnerabilities40 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4
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.

31At Risk · 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
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno data
0/8Automated maintenanceno data
0/10OpenSSF Scorecard: Pinned-Dependenciesno data
Inputs used
has_nixno
has_testsyes
lockfilesGemfile.lock
has_dockerfileno
typed_languageno
bootstrap_files
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 codeRuby without a type-check config
55/55Manageable file sizes0/50 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes50,186
source_files_sampled50
oversized_source_files0

Key facts

1,162GitHub stars
54contributors
34commits, last 12 months
38days since last push
84releases
1bus factor
9open issues
RubyGemspackage ecosystems

More detail

OpenSSF Scorecard 4.0 / 10
4.0aggregate

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-20 14:27 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
10CI-Tests3 out of 3 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 3/27 approved changesets -- score normalized to 1
6Contributorsproject has 2 contributing companies or organizations -- score normalized to 6
n/aDangerous-Workflowno workflows found
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
8Maintained8 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 8
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
0Vulnerabilities40 existing vulnerabilities detected
Direct dependencies 26
RegistryPackageVersion constraintManifest
RubyGemspryGemfile
RubyGemsrake< 14.0Gemfile
RubyGemsnokogiri~> 1.8.2Gemfile
RubyGemsnokogiri~> 1.16Gemfile
RubyGemsnokogiri~> 1.15Gemfile
RubyGemsnokogiri~> 1.10Gemfile
RubyGemsrspecGemfile
RubyGemsrspec= 2.14.1Gemfile
RubyGemssimplecovGemfile
RubyGemsbenchmark-ipsGemfile
RubyGemsbenchmark-memoryGemfile
RubyGemsrack-cache= 1.2Gemfile
RubyGemsjson= 2.3.1Gemfile
RubyGemsprygemfiles/Gemfile
RubyGemsrake< 14.0gemfiles/Gemfile
RubyGemsnokogiri~> 1.8.2gemfiles/Gemfile
RubyGemsnokogiri~> 1.16gemfiles/Gemfile
RubyGemsnokogiri~> 1.15gemfiles/Gemfile
RubyGemsnokogiri~> 1.10gemfiles/Gemfile
RubyGemsrspecgemfiles/Gemfile
RubyGemsrspec= 3.10.0gemfiles/Gemfile
RubyGemssimplecovgemfiles/Gemfile
RubyGemsbenchmark-ipsgemfiles/Gemfile
RubyGemsbenchmark-memorygemfiles/Gemfile
RubyGemsrack-cache= 1.2gemfiles/Gemfile
RubyGemsjson= 2.3.1gemfiles/Gemfile
All dependencies 30

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

RegistryPackageVersionRelation
RubyGemsbenchmark-ipsdirect
RubyGemsbenchmark-ips2.12.0direct
RubyGemsbenchmark-memorydirect
RubyGemsbenchmark-memory0.2.0direct
RubyGemsjson2.3.1direct
RubyGemsnokogiridirect
RubyGemsnokogiri1.15.4direct
RubyGemsprydirect
RubyGemspry0.11.3direct
RubyGemsrack-cache1.2direct
RubyGemsrakedirect
RubyGemsrake13.0.1direct
RubyGemsrspecdirect
RubyGemsrspec2.14.1direct
RubyGemsrspec3.10.0direct
RubyGemssimplecovdirect
RubyGemssimplecov0.22.0direct
RubyGemscoderay1.1.2indirect
RubyGemsdiff-lcs1.2.5indirect
RubyGemsdocile1.4.0indirect
RubyGemsmemory_profiler1.0.1indirect
RubyGemsmethod_source0.9.0indirect
RubyGemsmini_portile22.8.4indirect
RubyGemsracc1.7.1indirect
RubyGemsrack3.0.7indirect
RubyGemsrspec-core2.14.8indirect
RubyGemsrspec-expectations2.14.5indirect
RubyGemsrspec-mocks2.14.6indirect
RubyGemssimplecov-html0.12.3indirect
RubyGemssimplecov_json_formatter0.1.4indirect
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.15.0 — full methodology · metrics wiki.

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