Public record
Software health reportschema 0.16.0 · metrics 2.10.0 · 2026-07-20 15:49 UTC

drwl / annotaterb

A Ruby Gem that adds annotations to your Rails models and route files.

RubyCustom license★ 610 stars⑂ 88 forkssince Jun 2022View on GitHub ↗

drwl/annotaterb holds a health index of 84 out of 100, placing it in the Excellent band. It scores highest on Vitality (81/100) and lowest on AI Readiness (36/100). It was last updated 2 days ago. 4 contributors account for most of its recent work.

84
overall / 100
Excellent

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.

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

Ownership

Andrew W. LeePersonal account
16 followers12 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
RubyGemsannotaterb4.23.0-3125 days ago

Metrics by category

Vitality

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

81Excellent · 21% of overall
How it's scored
36/36Push recencylast push 2 days ago
17.3/36Commit cadence25/52 weeks with commits
17.3/18Commit volume83 commits in the last year
10/10OpenSSF Scorecard: Maintained25 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year83
human_commit_share
days_since_last_push2
active_weeks_last_year25
How it's scored
16.2/27Ships releases31 version tags (no GitHub releases)
36/36Release recencylatest release 25 days ago
19.8/27Release cadencea release every ~50 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count31
latest_release_tagv4.23.0
releases_from_tagsyes
days_since_latest_release25
mean_days_between_releases50
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?

71Good · 17% of overall
How it's scored
45.2/60Stars610 stars
16.2/25Forks88 forks
3.3/15Watchers5 watchers
Inputs used
forks88
stars610
watchers5
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
How it's scored
73.3/80Total downloads11,325,815 downloads all-time across rubygems
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesannotaterb
dependents
ecosystemsrubygems
total_downloads11,325,815
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?

80Excellent · 23% of overall
How it's scored
43.2/54Bus factor4 contributor(s) cover half of all commits
18.2/22.5Commit distributiontop contributor authored 19% of commits
13.5/13.5Contributor breadth100 contributors
10/10OpenSSF Scorecard: Contributorsproject has 39 contributing companies or organizations
Inputs used
bus_factor4
contributors_sampled100
top_contributor_share0.193
How it's scored
38/42Issue resolution90% of issues closed
27.5/30PR acceptance248/271 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
12/15OpenSSF Scorecard: Code-ReviewFound 25/29 approved changesets -- score normalized to 8
Inputs used
merged_prs248
open_issues8
closed_issues75
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio0.904
closed_unmerged_prs23
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.8/25Owner reach16 followers of drwl
20.1/25Track record12 public repos, account ~14 yr old
Inputs used
followers16
owner_typeUser
is_verified
owner_logindrwl
public_repos12
account_age_days5,294
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 25 days ago
20/20Version history31 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesannotaterb
ecosystemsrubygems
any_deprecatedno
min_days_since_publish25

Engineering Quality

Are baseline engineering and documentation practices in place?

61Moderate · 19% of overall
How it's scored
24/24CI workflows2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

50Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics4 topics
0/10Wiki
Inputs used
topicsactiverecord, annotations, rails, ruby
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?

68Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests30 out of 30 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
6/7.5Code-ReviewFound 25/29 approved changesets -- score normalized to 8
2.5/2.5Contributorsproject has 39 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.2/2.5Licenselicense file detected
7.5/7.5Maintained25 commit(s) and 12 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
5/5SASTSAST tool is run on all commits
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.9
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. 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
0/18One-command bootstrap
22/22Automated tests
0/11Lint / format config
0/11Static type checking
0/10Reproducible environment
0/10Demonstrated agent practiceno data
5/8Automated maintenancedependency automation configured, none observed in the sampled commits
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share
toolchain_manifests
dependency_bot_commit_share0
Excluded from scoring (no data or not applicable): Demonstrated agent practice. Remaining weights renormalized.
How it's scored
0/45Type-checkable codeRuby without a type-check config
55/55Manageable file sizes0/237 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes53,962
source_files_sampled237
oversized_source_files0
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexample
Inputs used
example_dirsexample
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

610GitHub stars
100contributors
83commits, last 12 months
2days since last push
31releases
4bus factor
8open issues
RubyGemspackage ecosystems

Data collection warnings

  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 6.9 / 10
6.9aggregate

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 15:48 UTC

10Binary-Artifactsno binaries found in the repo
n/aBranch-Protectioninternal error: error during branchesHandler.setup: internal error: some github tokens can't read classic branch protection rules: https://github.com/ossf/scorecard-action/blob/main/docs/authentication/fine-grained-auth-token.md
10CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
8Code-ReviewFound 25/29 approved changesets -- score normalized to 8
10Contributorsproject has 39 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained25 commit(s) and 12 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
10SASTSAST tool is run on all commits
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
RubyGemsrakeGemfile
RubyGemsbigdecimalGemfile
RubyGemsmutex_mGemfile
All dependencies 22

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

RegistryPackageVersionRelation
RubyGemsbigdecimaldirect
RubyGemsmutex_mdirect
RubyGemsrakedirect
RubyGemsactiverecordindirect
RubyGemsactivesupportindirect
RubyGemsannotaterbindirect
RubyGemsarubaindirect
RubyGemsbenchmarkindirect
RubyGemsbyebugindirect
RubyGemsguard-rspecindirect
RubyGemsloggerindirect
RubyGemsmysql2indirect
RubyGemsostructindirect
RubyGemspgindirect
RubyGemspryindirect
RubyGemspry-byebugindirect
RubyGemspumaindirect
RubyGemsrspecindirect
RubyGemssqlite3indirect
RubyGemsstandardindirect
RubyGemsterminal-notifier-guardindirect
RubyGemsweb-consoleindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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

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