Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-14 23:58 UTC

AnjanJ / rails_error_dashboard

Self-hosted error tracking for Rails - zero recurring cost, full data ownership.

Ruby · HTMLMIT★ 92 stars⑂ 9 forkssince Dec 2025View on GitHub ↗
KindLibraryNetwork servicehow this is determined

AnjanJ/rails_error_dashboard holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Vitality (90/100) and lowest on Security (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Anjan JagirdarPersonal account
15 followers18 public repossince Sep 2011

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
RubyGemsrails_error_dashboard0.11.9-900 days ago

Metrics by category

Vitality

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

90Excellent · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
18.7/36Commit cadence — 27/52 weeks with commits
18/18Commit volume — 681 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year681
human_commit_share0.75
days_since_last_push0
active_weeks_last_year27

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 81 releases published
36/36Release recency — latest release 0 days ago
27/27Release cadence — a release every ~2.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count81
latest_release_tagrails_error_dashboard/v0.11.9
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases2.1
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?

63Moderate · 17% of overall
How it's scored
31.8/60Stars — 92 stars
7.5/25Forks — 9 forks
0/15Watchers — 1 watchers
Inputs used
forks9
stars92
watchers1
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (MIT)
18/18CONTRIBUTING guide
13.5/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges8
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, github.com, shields.io
has_pull_request_templateyes
How it's scored
48.3/80Total downloads — 44,627 downloads all-time across rubygems
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesrails_error_dashboard
dependents—
ecosystemsrubygems
total_downloads44,627
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?

57Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.9/22.5Commit distribution — top contributor authored 96% of commits
12.2/13.5Contributor breadth — 9 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.96
How it's scored
34.1/42Issue resolution — 81% of issues closed
18.9/30PR acceptance — 84/133 decided PRs merged
13/13Newcomer PR acceptance — 1/1 first-time contributors' PRs merged in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/20 approved changesets -- score normalized to 1
Inputs used
merged_prs84
open_issues14
closed_issues60
prs_merged_7d6
prs_decided_7d6
prs_merged_30d33
prs_decided_30d35
issue_closed_ratio0.811
closed_unmerged_prs49
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
8.7/25Owner reach — 15 followers of AnjanJ
21.3/25Track record — 18 public repos, account ~15 yr old
Inputs used
followers15
owner_typeUser
is_verified—
owner_loginAnjanJ
public_repos18
account_age_days5,483
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 — 90 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesrails_error_dashboard
ecosystemsrubygems
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

86Excellent · 19% of overall
How it's scored
24/24CI workflows — 5 workflow(s)
24/24Tests present
16/16Linter config — .rubocop.yml
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 30 out of 30 merged PRs checked by a CI test -- score normalized to 10
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://anjanj.github.io/rails_error_dashboard/
10/10Repository description
10/10Topics — 18 topics
0/10Wiki
Inputs used
topicserror-monitoring, open-source, rails, ruby, self-hosted, error-dashboard, bug-tracking, devtools, error-reporting, error-tracking, exception-tracking, free, indie-hackers, monitoring, notifications, observability, rails-engine, ruby-gem
has_wikino
homepagehttps://anjanj.github.io/rails_error_dashboard/
docs_sitehttps://anjanj.github.io/rails_error_dashboard/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

47Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
2.2/7.5Branch-Protection — branch protection is not maximal on development and all release branches
2.5/2.5CI-Tests — 30 out of 30 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.8/7.5Code-Review — Found 2/20 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — 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
7.5/7.5Maintained — 30 commit(s) and 15 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
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
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.7
Excluded from scoring (no data or not applicable): 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.

69Good · 4% of overall
How it's scored
45/45Agent instructions — CLAUDE.md
15/15Machine-readable docs (llms.txt) — llms.txt served by the project website (https://anjanj.github.io/rails_error_dashboard/llms.txt)
40/40Legible commit history — 75 of 75 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtyes
llms_txt_urlhttps://anjanj.github.io/rails_error_dashboard/llms.txt
legible_history_share1
agent_instruction_filesCLAUDE.md
agent_instruction_max_bytes6,795
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .rubocop.yml
0/11Static type checking
0/10Reproducible environment
10/10Demonstrated agent practice — 45 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance — 4 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_testsyes
lockfiles—
has_dockerfileno
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0.45
toolchain_manifests—
dependency_bot_commit_share0.04
How it's scored
0/45Type-checkable code — Ruby without a type-check config
55/55Manageable file sizes — 0/549 source files over 60KB
Inputs used
primary_languageRuby
largest_source_bytes53,771
source_files_sampled549
oversized_source_files0

Key facts

92GitHub stars
9contributors
681commits, last 12 months
0days since last push
81releases
1bus factor
14open issues
RubyGemspackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

More detail

Star and fork history 0 ★ / 9 ⇿
0Stars
9Forks
65Releases

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.

0246810912026-012026-052026-09
Major 0Minor 6Patch 38
OpenSSF Scorecard 4.7 / 10
4.7aggregate

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-09-14 23:58 UTC

10Binary-Artifactsno binaries found in the repo
3Branch-Protectionbranch protection is not maximal on development and all release branches
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
1Code-ReviewFound 2/20 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
0Dangerous-Workflowdangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained30 commit(s) and 15 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
0SASTSAST tool is not run on all commits -- score normalized to 0
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 15
RegistryPackageVersion constraintManifest
RubyGemsrails—Gemfile
RubyGemsjson< 3Gemfile
RubyGemspuma—Gemfile
RubyGemspg—Gemfile
RubyGemstrilogy—Gemfile
RubyGemssqlite3~> 1.4Gemfile
RubyGemssqlite3>= 2.1Gemfile
RubyGemsrubocop-rails-omakase—Gemfile
RubyGemslefthook~> 2.0Gemfile
RubyGemsbundler-audit—Gemfile
RubyGemsbrowser~> 6.0Gemfile
RubyGemschartkick~> 5.0Gemfile
RubyGemshttparty>= 0.24Gemfile
RubyGemsrack-attack~> 6.7Gemfile
RubyGemsturbo-rails~> 2.0Gemfile
All dependencies not collected

The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository

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.