Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-12 03:06 UTC

reidmorrison / semantic_logger

Semantic Logger is a high-performance, asynchronous structured logging framework for Ruby and Rails.

RubyApache-2.0★ 956 stars⑂ 139 forkssince Aug 2012View on GitHub ↗

reidmorrison/semantic_logger holds a health index of 83 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (84/100) and lowest on Security (40/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Reid MorrisonPersonal account
106 followers25 public repossince Oct 2009

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
RubyGemssemantic_logger5.1.0-10353 days ago

Metrics by category

Vitality

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

73Good · 21% of overall
How it's scored
36/36Push recency — last push 5 days ago
12.5/36Commit cadence — 18/52 weeks with commits
18/18Commit volume — 174 commits in the last year
0/10OpenSSF Scorecard: Maintained — no data
Inputs used
commits_last_year174
human_commit_share1
days_since_last_push5
active_weeks_last_year18
How it's scored
16.2/27Ships releases — 56 version tags (no GitHub releases)
36/36Release recency — latest release 53 days ago
12.6/27Release cadence — a release every ~151 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count56
latest_release_tagv5.1.0
releases_from_tagsyes
days_since_latest_release53
mean_days_between_releases151

Community & Adoption

Does the project have users, downloads, attention, and a welcoming setup for contributors?

84Excellent · 17% of overall
How it's scored
48.3/60Stars — 956 stars
17.8/25Forks — 139 forks
7.5/15Watchers — 23 watchers
Inputs used
forks139
stars956
watchers23
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

85Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
7.2/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingyes
has_issue_templateyes
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes
How it's scored
78.7/80Total downloads — 37,210,488 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagessemantic_logger
dependents—
ecosystemsrubygems
total_downloads37,210,488
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?

67Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
4.5/22.5Commit distribution — top contributor authored 80% of commits
13.5/13.5Contributor breadth — 82 contributors
0/10OpenSSF Scorecard: Contributors — no data
Inputs used
bus_factor1
contributors_sampled82
top_contributor_share0.8
How it's scored
42/42Issue resolution — 100% of issues closed
25.3/30PR acceptance — 166/197 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
0/15OpenSSF Scorecard: Code-Review — no data
Inputs used
merged_prs166
open_issues0
closed_issues160
prs_merged_7d4
prs_decided_7d4
prs_merged_30d7
prs_decided_30d7
issue_closed_ratio1
closed_unmerged_prs31
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
14.6/25Owner reach — 106 followers of reidmorrison
22.3/25Track record — 25 public repos, account ~16 yr old
Inputs used
followers106
owner_typeUser
is_verified—
owner_loginreidmorrison
public_repos25
account_age_days6,160
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 53 days ago
20/20Version history — 103 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagessemantic_logger
ecosystemsrubygems
any_deprecatedno
min_days_since_publish53

Engineering Quality

Are baseline engineering and documentation practices in place?

84Excellent · 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 — no data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configno

Documentation

90Excellent
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://logger.reidmorrison.com/
10/10Repository description
10/10Topics — 6 topics
0/10Wiki
Inputs used
topicslogging, rails-semantic-logger, bugsnag, syslog, splunk, elasticsearch
has_wikino
homepagehttps://logger.reidmorrison.com/
docs_sitehttps://logger.reidmorrison.com/
has_readmeyes
has_docs_diryes
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
30/30Security policy (SECURITY.md)
0/25Dependabot config
0/25Dependency lockfiles — published library — lockfiles are an application concern, not expected
0/20CodeQL workflow
Inputs used
sourcefile_signals
lockfiles—
manifestsGemfile, docs/Gemfile
has_codeql_workflowno
has_security_policyyes
has_dependabot_configno
Excluded from scoring (no data or not applicable): Dependency lockfiles. 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.

73Good · 4% of overall
How it's scored
45/45Agent instructions — AGENTS.md, CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt present
40/40Legible commit history — 90 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_url—
legible_history_share0.9
agent_instruction_filesAGENTS.md, CLAUDE.md
agent_instruction_max_bytes15,634
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
10/10Reproducible environment — Dockerfile
10/10Demonstrated agent practice — 53 of the last 100 commits agent-authored or agent-credited
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — no data
Inputs used
has_nixno
has_testsyes
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.53
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/150 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes29,649
source_files_sampled150
oversized_source_files0

Key facts

956GitHub stars
82contributors
174commits, last 12 months
5days since last push
56releases
1bus factor
0open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • No resolved dependencies carried a version and a supported ecosystem
  • OpenSSF Scorecard timed out after 240s; skipping Scorecard checks

More detail

Star and fork history 0 ★ / 139 ⇿
0Stars
139Forks
55Releases

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.

025507510012515013932013-102020-032026-08
Major 3Minor 36Patch 16

Each point covers 12 days.

Direct dependencies 33
RegistryPackageVersion constraintManifest
RubyGemsamazing_print—Gemfile
RubyGemsminitest~> 6.0Gemfile
RubyGemsminitest-mock—Gemfile
RubyGemsminitest-reporters—Gemfile
RubyGemsminitest-shared_description—Gemfile
RubyGemsminitest-stub_any_instance—Gemfile
RubyGemsrake—Gemfile
RubyGemsrspec—Gemfile
RubyGemssimplecov—Gemfile
RubyGemssolargraph—Gemfile
RubyGemsbugsnag—Gemfile
RubyGemsbunny—Gemfile
RubyGemselasticsearch~>7.13.0Gemfile
RubyGemsopensearch-ruby—Gemfile
RubyGemsgelf—Gemfile
RubyGemshoneybadger—Gemfile
RubyGemsruby-kafka—Gemfile
RubyGemsbase64—Gemfile
RubyGemsmongo—Gemfile
RubyGemsopentelemetry-logs-sdk—Gemfile
RubyGemsnet_tcp_client—Gemfile
RubyGemsnokogiri—Gemfile
RubyGemssplunk-sdk-ruby—Gemfile
RubyGemsstatsd-ruby—Gemfile
RubyGemssentry-raven—Gemfile
RubyGemssentry-ruby—Gemfile
RubyGemssyslog—Gemfile
RubyGemssyslog_protocol—Gemfile
RubyGemsaws-sdk-cloudwatchlogs—Gemfile
RubyGemsrubocop~> 1.79.0Gemfile
RubyGemsrubocop-minitest—Gemfile
RubyGemsrubocop-rake—Gemfile
RubyGemsrubocop-rspec—Gemfile
All dependencies 35

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

RegistryPackageVersionRelation
RubyGemsamazing_print—direct
RubyGemsaws-sdk-cloudwatchlogs—direct
RubyGemsbase64—direct
RubyGemsbugsnag—direct
RubyGemsbunny—direct
RubyGemselasticsearch—direct
RubyGemsgelf—direct
RubyGemshoneybadger—direct
RubyGemsminitest—direct
RubyGemsminitest-mock—direct
RubyGemsminitest-reporters—direct
RubyGemsminitest-shared_description—direct
RubyGemsminitest-stub_any_instance—direct
RubyGemsmongo—direct
RubyGemsnet_tcp_client—direct
RubyGemsnokogiri—direct
RubyGemsopensearch-ruby—direct
RubyGemsopentelemetry-logs-sdk—direct
RubyGemsrake—direct
RubyGemsrspec—direct
RubyGemsrubocop—direct
RubyGemsrubocop-minitest—direct
RubyGemsrubocop-rake—direct
RubyGemsrubocop-rspec—direct
RubyGemsruby-kafka—direct
RubyGemssentry-raven—direct
RubyGemssentry-ruby—direct
RubyGemssimplecov—direct
RubyGemssolargraph—direct
RubyGemssplunk-sdk-ruby—direct
RubyGemsstatsd-ruby—direct
RubyGemssyslog—direct
RubyGemssyslog_protocol—direct
RubyGemsconcurrent-ruby—indirect
RubyGemsgithub-pages—indirect
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.34.0 — full methodology · metrics wiki.

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