Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 13:36 UTC

jonashellmann / everydocs-core

A simple Document Management System for private use with basic functionality to organize your documents digitally

RubyGPL-3.0★ 412 stars⑂ 22 forkssince May 2019View on GitHub ↗
KindNetwork servicehow this is determined

jonashellmann/everydocs-core holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Security (72/100) and lowest on AI Readiness (35/100). It was last updated 46 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Jonas HellmannPersonal account
31 followers17 public repossince Oct 2015ALTE OLDENBURGER Krankenversicherung GmbH

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Metrics by category

Vitality

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

45Weak · 21% of overall
How it's scored
18/36Push recency — last push 46 days ago
9.7/36Commit cadence — 14/52 weeks with commits
13.6/18Commit volume — 32 commits in the last year
5/10OpenSSF Scorecard: Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year32
human_commit_share0.97
days_since_last_push46
active_weeks_last_year14
How it's scored
27/27Ships releases — 1 releases published
0/36Release recency — latest release 2,530 days ago
12.6/27Release cadence — cadence unknown (single release)
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count1
latest_release_tagv1.0
releases_from_tagsno
days_since_latest_release2,530
mean_days_between_releases—
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?

53Moderate · 17% of overall
How it's scored
42.4/60Stars — 412 stars
11/25Forks — 22 forks
2.7/15Watchers — 4 watchers
Inputs used
forks22
stars412
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (GPL-3.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges5
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

43Weak · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
0.1/22.5Commit distribution — top contributor authored 100% of commits
2.7/13.5Contributor breadth — 2 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.995
How it's scored
42/42Issue resolution — 100% of issues closed
16.6/30PR acceptance — 57/103 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/13 approved changesets -- score normalized to 1
Inputs used
merged_prs57
open_issues0
closed_issues7
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs46
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
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
10.8/25Owner reach — 31 followers of jonashellmann
21.1/25Track record — 17 public repos, account ~10 yr old
Inputs used
followers31
owner_typeUser
is_verified—
owner_loginjonashellmann
public_repos17
account_age_days3,986
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

65Good · 19% of overall
How it's scored
24/24CI workflows — 2 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests — 13 out of 13 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

60Moderate
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
10/10Repository description
10/10Topics — 2 topics
10/10Wiki
Inputs used
topicsdocument-management, document
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?

72Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
2.5/2.5CI-Tests — 13 out of 13 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/13 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
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
3.8/7.5Maintained — 6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
4.5/5SAST — SAST tool is not run on all commits -- score normalized to 9
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
7.5/7.5Token-Permissions — GitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.4
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, 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
advisories0
affected_packages0
assessed_packages98
unassessed_packages0
affected_by_severitynone
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 98 resolved dependencies against OSV. 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.

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

Key facts

412GitHub stars
2contributors
32commits, last 12 months
46days since last push
1releases
1bus factor
0open 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 ★ / 22 ⇿
0Stars
22Forks

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.

048121620242212021-072024-012026-08

Each point covers 5 days.

OpenSSF Scorecard 6.4 / 10
6.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-09-19 13:36 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-Tests13 out of 13 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/13 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained6 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
0Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
9SASTSAST tool is not run on all commits -- score normalized to 9
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 16
RegistryPackageVersion constraintManifest
RubyGemsrails>= 8.0.4.1Gemfile
RubyGemssqlite3>= 2.1Gemfile
RubyGemsmysql2~> 0.5Gemfile
RubyGemssassc-rails—Gemfile
RubyGemsuglifier>= 1.3.0Gemfile
RubyGemsjquery-rails—Gemfile
RubyGemsturbolinks—Gemfile
RubyGemsjbuilder~> 2.0Gemfile
RubyGemssdoc~> 1.1.0Gemfile
RubyGemsbcrypt~> 3.1.7Gemfile
RubyGemsjwt—Gemfile
RubyGemsconfig—Gemfile
RubyGemspdf-reader—Gemfile
RubyGemswebrick>=1.8.2Gemfile
RubyGemsrack-cors—Gemfile
RubyGemslockbox=1.3.3Gemfile
All dependencies 98

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

RegistryPackageVersionRelation
RubyGemsbcrypt3.1.22direct
RubyGemsconfig5.6.1direct
RubyGemsjbuilder2.15.1direct
RubyGemsjquery-rails4.6.1direct
RubyGemsjwt3.2.0direct
RubyGemslockbox1.3.3direct
RubyGemsmysql20.5.7direct
RubyGemspdf-reader2.15.1direct
RubyGemsrack-cors3.0.0direct
RubyGemsrails8.0.5.1direct
RubyGemssassc-rails2.1.2direct
RubyGemssdoc1.1.0direct
RubyGemssqlite32.9.5direct
RubyGemsturbolinks5.2.1direct
RubyGemsuglifier4.2.1direct
RubyGemswebrick1.9.2direct
RubyGemsactioncable8.0.5.1indirect
RubyGemsactionmailbox8.0.5.1indirect
RubyGemsactionmailer8.0.5.1indirect
RubyGemsactionpack8.0.5.1indirect
RubyGemsactiontext8.0.5.1indirect
RubyGemsactionview8.0.5.1indirect
RubyGemsactivejob8.0.5.1indirect
RubyGemsactivemodel8.0.5.1indirect
RubyGemsactiverecord8.0.5.1indirect
RubyGemsactivestorage8.0.5.1indirect
RubyGemsactivesupport8.0.5.1indirect
RubyGemsafm1.0.0indirect
RubyGemsAscii852.0.1indirect
RubyGemsbase640.3.0indirect
RubyGemsbenchmark0.5.0indirect
RubyGemsbigdecimal4.1.2indirect
RubyGemsbinding_of_caller2.0.0indirect
RubyGemsbuilder3.3.0indirect
RubyGemsbyebug13.0.0indirect
RubyGemsconcurrent-ruby1.3.8indirect
RubyGemsconnection_pool3.0.2indirect
RubyGemscrass1.0.7indirect
RubyGemsdate3.5.1indirect
RubyGemsdebug_inspector1.2.0indirect
RubyGemsdeep_merge1.2.2indirect
RubyGemsdrb2.2.3indirect
RubyGemserb6.0.6indirect
RubyGemserubi1.13.1indirect
RubyGemsexecjs2.10.1indirect
RubyGemsffi1.17.4indirect
RubyGemsglobalid1.4.0indirect
RubyGemshashery2.1.2indirect
RubyGemsi18n1.15.2indirect
RubyGemsio-console0.8.2indirect
RubyGemsirb1.18.0indirect
RubyGemslogger1.7.0indirect
RubyGemsloofah2.25.2indirect
RubyGemsmail2.9.1indirect
RubyGemsmarcel1.2.1indirect
RubyGemsmini_mime1.1.5indirect
RubyGemsminitest6.0.6indirect
RubyGemsnet-imap0.6.6indirect
RubyGemsnet-pop0.1.2indirect
RubyGemsnet-protocol0.2.2indirect
RubyGemsnet-smtp0.5.1indirect
RubyGemsnio4r2.7.5indirect
RubyGemsnokogiri1.19.4indirect
RubyGemsostruct0.6.3indirect
RubyGemspp0.6.4indirect
RubyGemsprettyprint0.2.0indirect
RubyGemsprism1.9.0indirect
RubyGemsracc1.8.1indirect
RubyGemsrack3.2.6indirect
RubyGemsrack-session2.1.2indirect
RubyGemsrack-test2.2.0indirect
RubyGemsrackup2.3.1indirect
RubyGemsrails-dom-testing2.3.0indirect
RubyGemsrails-html-sanitizer1.7.1indirect
RubyGemsrailties8.0.5.1indirect
RubyGemsrake13.4.2indirect
RubyGemsrbs4.1.2indirect
RubyGemsrdoc8.0.0indirect
RubyGemsreline0.6.3indirect
RubyGemsruby-rc40.1.5indirect
RubyGemssassc2.4.0indirect
RubyGemssecurerandom0.4.1indirect
RubyGemsspring4.7.0indirect
RubyGemssprockets4.2.2indirect
RubyGemssprockets-rails3.5.2indirect
RubyGemsthor1.5.0indirect
RubyGemstilt2.8.0indirect
RubyGemstimeout0.6.1indirect
RubyGemstsort0.2.0indirect
RubyGemsttfunk1.7.0indirect
RubyGemsturbolinks-source5.2.0indirect
RubyGemstzinfo2.0.6indirect
RubyGemsuri1.1.1indirect
RubyGemsuseragent0.16.11indirect
RubyGemsweb-console2.3.0indirect
RubyGemswebsocket-driver0.8.2indirect
RubyGemswebsocket-extensions0.1.5indirect
RubyGemszeitwerk2.8.3indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 98 packages, which also include development and test pins that never ship: 0 carry known advisories, of which 0 are direct.

No known advisories affect the assessed dependencies.

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

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.