Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-16 09:00 UTC

Textualize / rich

Rich is a Python library for rich text and beautiful formatting in the terminal.

PythonMIT★ 57,366 stars⑂ 2,349 forkssince Nov 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

Textualize/rich holds a health index of 91 out of 100, placing it in the Excellent band. It scores highest on Community & Adoption (97/100) and lowest on AI Readiness (65/100). It was last updated 85 days ago. 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

TextualizeOrganization
2,372 followers33 public repossince Oct 2021

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
PyPIrich15.0.0592,951,204207157 days ago

Metrics by category

Vitality

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

65Good · 21% of overall
How it's scored
18/36Push recency — last push 85 days ago
11.8/36Commit cadence — 17/52 weeks with commits
18/18Commit volume — 173 commits in the last year
5/10OpenSSF Scorecard: Maintained — 2 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year173
human_commit_share0.98
days_since_last_push85
active_weeks_last_year17
How it's scored
27/27Ships releases — 100 releases published
27/36Release recency — latest release 157 days ago
19.8/27Release cadence — a release every ~58.4 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv15.0.0
releases_from_tagsno
days_since_latest_release157
mean_days_between_releases58.4
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?

97Exceptional · 17% of overall

Popularity & adoption

100Exceptional
How it's scored
60/60Stars — 57,366 stars
25/25Forks — 2,349 forks
15/15Watchers — 529 watchers
Inputs used
forks2,349
stars57,366
watchers529
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_badges5
has_contributingyes
has_issue_templateno
has_code_of_conductyes
readme_badge_servicesbadge.fury.io, shields.io
has_pull_request_templateyes
How it's scored
80/80Monthly downloads — 592,951,204 downloads/month across pypi
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesrich
dependents—
ecosystemspypi
total_downloads—
monthly_downloads592,951,204
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?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
5.5/22.5Commit distribution — top contributor authored 76% of commits
13.5/13.5Contributor breadth — 99 contributors
10/10OpenSSF Scorecard: Contributors — project has 52 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled99
top_contributor_share0.757
How it's scored
35.4/42Issue resolution — 84% of issues closed
19/30PR acceptance — 870/1,372 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 1/10 approved changesets -- score normalized to 1
Inputs used
merged_prs870
open_issues241
closed_issues1,290
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.843
closed_unmerged_prs502
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
30/30Ownership backing — organization-owned
0/20Verified domain
24.3/25Owner reach — 2,372 followers of Textualize
20.9/25Track record — 33 public repos, account ~4 yr old
Inputs used
followers2,372
owner_typeOrganization
is_verifiedno
owner_loginTextualize
public_repos33
account_age_days1,782

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on pypi
35/35Publish recency — latest publish 157 days ago
20/20Version history — 207 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesrich
ecosystemspypi
any_deprecatedno
min_days_since_publish157

Engineering Quality

Are baseline engineering and documentation practices in place?

94Exceptional · 19% of overall
How it's scored
24/24CI workflows — 6 workflow(s)
24/24Tests present
16/16Linter config — pyproject.toml ([tool.isort]), tox.ini
9.6/9.6Pre-commit hooks
0/6.4.editorconfig
16/20OpenSSF Scorecard: CI-Tests — 6 out of 7 merged PRs checked by a CI test -- score normalized to 8
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configyes
has_precommit_configyes

Documentation

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage site — https://rich.readthedocs.io/en/latest/
10/10Repository description
10/10Topics — 16 topics
10/10Wiki
Inputs used
topicspython, python3, python-library, terminal, terminal-color, markdown, tables, syntax-highlighting, ansi-colors, progress-bar-python, progress-bar, traceback, rich, tracebacks-rich, emoji, tui
has_wikiyes
homepagehttps://rich.readthedocs.io/en/latest/
docs_sitehttps://rich.readthedocs.io/en/latest/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

70Good · 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 — 6 out of 7 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
0.8/7.5Code-Review — Found 1/10 approved changesets -- score normalized to 1
2.5/2.5Contributors — project has 52 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
7.5/7.5Dependency-Update-Tool — update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 2 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
4.5/5SAST — SAST tool detected but not run on all commits
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
0.8/7.5Vulnerabilities — 9 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate6.2
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
25/25Indirect dependencies free of known advisories — no indirect dependency carries a known advisory
0/40No advisories left outstanding — no advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages3
unassessed_packages0
affected_by_severitynone
direct_affected_packages0
Excluded from scoring (no data or not applicable): No advisories left outstanding. Remaining weights renormalized. Matched the pypi:rich@15.0.0 runtime dependency closure — what installing the published package pulls in — 3 packages. 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.

65Good · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
14.1/40Legible commit history — 26 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.265
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile, docs/Makefile
22/22Automated tests
11/11Lint / format config — pyproject.toml ([tool.isort]), tox.ini
11/11Static type checking — rich/py.typed
10/10Reproducible environment — lockfile
6/10Demonstrated agent practice — 3 of the last 100 commits agent-authored or agent-credited
5/8Automated maintenance — dependency automation configured, none observed in the sampled commits
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
Inputs used
has_nixno
has_testsyes
lockfilespoetry.lock
has_dockerfileno
typed_languageno
bootstrap_filesMakefile, docs/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configsrich/py.typed
agent_commit_share0.03
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
27/45Type-checkable code — Python with type-check config (rich/py.typed)
54.2/55Manageable file sizes — 3/213 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes140,235
source_files_sampled213
oversized_source_files3
How it's scored
0/40API schema (OpenAPI/GraphQL/proto) — not applicable to this kind of software
0/20MCP server — not applicable to this kind of software
40/40Runnable examples — examples
Inputs used
example_dirsexamples
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

57,366GitHub stars
99contributors
173commits, last 12 months
85days since last push
100releases
1bus factor
241open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • pypi download statistics for 'rich' unavailable this scan (stats endpoint failed after retries); adoption may be under-evidenced
  • pypi download figures for rich carried forward from the previous scan (stats endpoint unavailable this scan)

More detail

Star and fork history 0 ★ / 2,349 ⇿
0Stars
2,349Forks
28Releases

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.

Only the most recent history is shown — this repository exceeds the collection window, so the earliest history is not captured.

1,2001,4001,6001,8002,0002,2002,4002,349192023-042024-122026-09
Major 2Minor 9Patch 17

Each point covers 4 days.

OpenSSF Scorecard 6.2 / 10
6.2aggregate

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-16 09:00 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-Tests6 out of 7 merged PRs checked by a CI test -- score normalized to 8
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 1/10 approved changesets -- score normalized to 1
10Contributorsproject has 52 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
5Maintained2 commit(s) and 4 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
9SASTSAST tool detected but not run on all commits
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
1Vulnerabilities9 existing vulnerabilities detected
Direct dependencies 3
RegistryPackageVersion constraintManifest
PyPIpygments^2.13.0pyproject.toml
PyPIipywidgets>=7.5.1,<9pyproject.toml
PyPImarkdown-it-py>=2.2.0pyproject.toml
All dependencies 53

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

RegistryPackageVersionRelation
PyPIipywidgets8.1.7direct
PyPImarkdown-it-py3.0.0direct
PyPIpygments2.19.2direct
PyPIalabaster1.0.0indirect
PyPIappnope0.1.4indirect
PyPIasttokens3.0.0indirect
PyPIattrs21.4.0indirect
PyPIbackcall0.2.0indirect
PyPIblack22.12.0indirect
PyPIcfgv3.4.0indirect
PyPIclick8.1.8indirect
PyPIcolorama0.4.6indirect
PyPIcomm0.2.3indirect
PyPIcoverage7.6.1indirect
PyPIdecorator5.2.1indirect
PyPIdistlib0.4.0indirect
PyPIexceptiongroup1.3.0indirect
PyPIexecuting2.2.1indirect
PyPIfilelock3.16.1indirect
PyPIidentify2.6.1indirect
PyPIiniconfig2.1.0indirect
PyPIipython8.12.3indirect
PyPIjedi0.19.2indirect
PyPIjupyterlab-widgets3.0.15indirect
PyPImatplotlib-inline0.1.7indirect
PyPImdurl0.1.2indirect
PyPImypy1.14.1indirect
PyPImypy-extensions1.1.0indirect
PyPInodeenv1.9.1indirect
PyPIpackaging25.0indirect
PyPIparso0.8.5indirect
PyPIpathspec0.12.1indirect
PyPIpexpect4.9.0indirect
PyPIpickleshare0.7.5indirect
PyPIplatformdirs4.3.6indirect
PyPIpluggy1.5.0indirect
PyPIpre-commit2.21.0indirect
PyPIprompt-toolkit3.0.52indirect
PyPIptyprocess0.7.0indirect
PyPIpure-eval0.2.3indirect
PyPIpytest7.4.4indirect
PyPIpytest-cov3.0.0indirect
PyPIpyyaml6.0.3indirect
PyPIsphinx8.2.3indirect
PyPIsphinx-copybutton0.5.2indirect
PyPIsphinx-rtd-theme3.0.2indirect
PyPIstack-data0.6.3indirect
PyPItomli2.3.0indirect
PyPItraitlets5.14.3indirect
PyPItyping-extensions4.13.2indirect
PyPIvirtualenv20.34.0indirect
PyPIwcwidth0.2.14indirect
PyPIwidgetsnbextension4.0.14indirect
Dependency advisories 0

Installing pypi:rich@15.0.0 pulls in 3 packages, direct and transitive: 0 carry known advisories, of which 0 are direct dependencies.

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 — PyPI.