Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-11 18:02 UTC

bookwyrm-social / bookwyrm

Social reading and reviewing, decentralized with ActivityPub

Python · HTMLCustom license★ 2,779 stars⑂ 335 forkssince Jan 2020View on GitHub ↗

bookwyrm-social/bookwyrm holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Vitality (99/100) and lowest on AI Readiness (47/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

BookWyrmOrganization
223 followers4 public repossince Apr 2021

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Metrics by category

Vitality

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

99Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 0 days ago
35.3/36Commit cadence — 51/52 weeks with commits
18/18Commit volume — 1,439 commits in the last year
10/10OpenSSF Scorecard: Maintained — 30 commit(s) and 12 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year1,439
human_commit_share0.97
days_since_last_push0
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 38 releases published
36/36Release recency — latest release 1 days ago
27/27Release cadence — a release every ~33.1 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count38
latest_release_tagv0.9.3
releases_from_tagsno
days_since_latest_release1
mean_days_between_releases33.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?

85Excellent · 17% of overall
How it's scored
55.9/60Stars — 2,779 stars
21/25Forks — 335 forks
8.2/15Watchers — 31 watchers
Inputs used
forks335
stars2,779
watchers31
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

86Excellent
How it's scored
22.5/22.5README
16.9/22.5License — license file present, not a recognized license
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_badges3
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateyes

Sustainability & Governance

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

55Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
6.4/22.5Commit distribution — top contributor authored 72% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 27 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.715
How it's scored
31.3/42Issue resolution — 75% of issues closed
27.6/30PR acceptance — 2,251/2,450 decided PRs merged
2.2/13Newcomer PR acceptance — 1/6 first-time contributors' PRs merged in 30d
6/15OpenSSF Scorecard: Code-Review — Found 5/11 approved changesets -- score normalized to 4
Inputs used
merged_prs2,251
open_issues400
closed_issues1,176
prs_merged_7d11
prs_decided_7d11
prs_merged_30d27
prs_decided_30d34
issue_closed_ratio0.746
closed_unmerged_prs199
first_time_authors_30d5
first_time_prs_merged_30d1
first_time_prs_decided_30d6
How it's scored
30/30Ownership backing — organization-owned
0/20Verified domain
16.9/25Owner reach — 223 followers of bookwyrm-social
15.9/25Track record — 4 public repos, account ~5 yr old
Inputs used
followers223
owner_typeOrganization
is_verifiedno
owner_loginbookwyrm-social
public_repos4
account_age_days1,977

Engineering Quality

Are baseline engineering and documentation practices in place?

78Good · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — .eslintrc.js, pyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 9 out of 11 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
15/15Documentation / homepage site — http://joinbookwyrm.com/
10/10Repository description
10/10Topics — 8 topics
0/10Wiki
Inputs used
topicsactivitypub, decentralization, federation, books, reading, social-media, openlibrary, bookwyrm
has_wikino
homepagehttp://joinbookwyrm.com/
docs_sitehttp://joinbookwyrm.com/
has_readmeyes
has_docs_dirno
has_descriptionyes

Security

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

75Good · 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/2.5CI-Tests — 9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
3/7.5Code-Review — Found 5/11 approved changesets -- score normalized to 4
2.5/2.5Contributors — project has 27 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
0/5Fuzzing — project is not fuzzed
2.2/2.5License — license file detected
7.5/7.5Maintained — 30 commit(s) and 12 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
4.5/5SAST — SAST tool detected but not run on all commits
4.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_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.

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
advisories1
affected_packages1
assessed_packages60
unassessed_packages12
affected_by_severitymoderate 1
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 60 resolved dependencies against OSV. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list. 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.

47Weak · 4% of overall
How it's scored
18/45Agent instructions — AGENTS.md (stub)
0/15Machine-readable docs (llms.txt)
19.8/40Legible commit history — 36 of 97 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.371
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes46
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format config — .eslintrc.js, pyproject.toml ([tool.ruff])
0/11Static type checking
10/10Reproducible environment — Dockerfile
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
lockfiles—
has_dockerfileyes
typed_languageno
bootstrap_files—
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0.03
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/787 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes56,214
source_files_sampled787
oversized_source_files0

Key facts

2,779GitHub stars
99contributors
1,439commits, last 12 months
0days since last push
38releases
1bus factor
400open issues
npm, PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

Star and fork history 0 ★ / 335 ⇿
0Stars
335Forks
38Releases

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.

012525037532772020-022023-052026-09
Major 0Minor 5Patch 33

Each point covers 7 days.

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-09-11 18:02 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
8CI-Tests9 out of 11 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
4Code-ReviewFound 5/11 approved changesets -- score normalized to 4
10Contributorsproject has 27 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
9Licenselicense file detected
10Maintained30 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
9SASTSAST tool detected but not run on all commits
9Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 72

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

RegistryPackageVersionRelation
npmbulma^0.9.3indirect
npmeslint^8.9.0indirect
npmmerge2.1.1indirect
npmprettier2.5.1indirect
npmstylelint^17.1.1indirect
npmstylelint-config-recommended^18.0.0indirect
npmstylelint-config-standard^40.0.0indirect
npmstylelint-config-standard-scss^17.0.0indirect
npmstylelint-order^7.0.1indirect
npmwatch^1.0.2indirect
PyPIaiohttp3.14.3indirect
PyPIarabic-reshaper3.0.1indirect
PyPIbleach6.4.0indirect
PyPIboto31.34.74indirect
PyPIbw-file-resubmit0.6.0rc2indirect
PyPIcelery5.6.2indirect
PyPIcelery-types0.22.0indirect
PyPIcolorthief0.2.1indirect
PyPIdjango5.2.16indirect
PyPIdjango-celery-beat2.8.1indirect
PyPIdjango-compressor4.6indirect
PyPIdjango-csp3.8indirect
PyPIdjango-imagekit6.0.0indirect
PyPIdjango-model-utils4.4.0indirect
PyPIdjango-oauth-toolkit3.2.0indirect
PyPIdjango-pgtrigger4.17.0indirect
PyPIdjango-sass-processor1.4.2indirect
PyPIdjango-storages1.14.6indirect
PyPIdjango-stubs4.2.7indirect
PyPIenvirons14.5.0indirect
PyPIfakeredis2.37.0indirect
PyPIflower2.0.1indirect
PyPIgrpcio—indirect
PyPIgunicorn25.0.3indirect
PyPIhiredis2.3.2indirect
PyPIlibsass0.23.0indirect
PyPImistune3.3.3indirect
PyPImypy1.7.1indirect
PyPIopentelemetry-api1.24.0indirect
PyPIopentelemetry-exporter-otlp-proto-grpc1.24.0indirect
PyPIopentelemetry-instrumentation-celery0.45b0indirect
PyPIopentelemetry-instrumentation-django0.45b0indirect
PyPIopentelemetry-instrumentation-psycopg0.45b0indirect
PyPIopentelemetry-sdk1.24.0indirect
PyPIpilkit—indirect
PyPIpillow12.3.0indirect
PyPIpsycopg3.2.9indirect
PyPIpycryptodome3.20.0indirect
PyPIpyotp2.9.0indirect
PyPIpytest9.0.3indirect
PyPIpytest-cov5.0.0indirect
PyPIpytest-django4.8.0indirect
PyPIpytest-env1.1.3indirect
PyPIpytest-xdist3.5.0indirect
PyPIpython-bidi0.6.10indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpytidylib0.3.2indirect
PyPIqrcode7.4.2indirect
PyPIredis5.0.3indirect
PyPIrequests2.33.0indirect
PyPIresponses0.25.0indirect
PyPIruff0.14.7indirect
PyPIs3-tar0.1.13indirect
PyPIsetuptools—indirect
PyPIsqlparse0.6.0indirect
PyPItornado—indirect
PyPItypes-bleach6.1.0.20240331indirect
PyPItypes-dataclasses0.6.6indirect
PyPItypes-pillow10.2.0.20240331indirect
PyPItypes-python-dateutil2.9.0.20240316indirect
PyPItypes-requests2.31.0.20240311indirect
PyPIua-parser1.0.1indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 60 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct. 12 could not be assessed — no resolved version, an unsupported ecosystem, or beyond the reported package list.

PackageVersionRelationSeverityAdvisoriesFixed in
django5.2.16indirectmoderate16.0.8

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.