Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-19 05:22 UTC

breezedeus / CnOCR

CnOCR: Awesome Chinese/English OCR Python toolkits based on PyTorch. It comes with 20+ well-trained models for different application scenarios and can be used directly after installation. 【基于 PyTorch/MXNet 的中文/英文 OCR Python 包。】

PythonApache-2.0★ 3,769 stars⑂ 534 forkssince Mar 2019forkView on GitHub ↗
KindCommand-line toolhow this is determined

breezedeus/CnOCR holds a health index of 48 out of 100, placing it in the Weak band. It scores highest on Community & Adoption (60/100) and lowest on Security (35/100). It was last updated 76 days ago. A single contributor accounts for most of its recent work.

48
overall / 100
Weak

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.

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

Ownership

BreezedeusPersonal account
480 followers49 public repossince Feb 2014

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?

55Moderate · 21% of overall
How it's scored
18/36Push recency — last push 76 days ago
2.1/36Commit cadence — 3/52 weeks with commits
10.8/18Commit volume — 15 commits in the last year
5/10OpenSSF Scorecard: Maintained — 5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year15
human_commit_share1
days_since_last_push76
active_weeks_last_year3
How it's scored
27/27Ships releases — 37 releases published
36/36Release recency — latest release 76 days ago
19.8/27Release cadence — a release every ~102.6 days
0/10OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases.
Inputs used
releases_count37
latest_release_tagv2.3.3
releases_from_tagsno
days_since_latest_release76
mean_days_between_releases102.6

Community & Adoption

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

60Moderate · 17% of overall
How it's scored
58/60Stars — 3,769 stars
22.7/25Forks — 534 forks
10.2/15Watchers — 69 watchers
Inputs used
forks534
stars3,769
watchers69
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5License — recognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges9
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesbadge.fury.io, readthedocs.org, shields.io
has_pull_request_templateno

Sustainability & Governance

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

54Moderate · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
1.1/22.5Commit distribution — top contributor authored 95% of commits
13.5/13.5Contributor breadth — 11 contributors
3/10OpenSSF Scorecard: Contributors — project has 1 contributing companies or organizations -- score normalized to 3
Inputs used
bus_factor1
contributors_sampled11
top_contributor_share0.951
How it's scored
33.6/42Issue resolution — 80% of issues closed
29.7/30PR acceptance — 103/104 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
1.5/15OpenSSF Scorecard: Code-Review — Found 2/11 approved changesets -- score normalized to 1
Inputs used
merged_prs103
open_issues53
closed_issues214
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio0.801
closed_unmerged_prs1
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
19.3/25Owner reach — 480 followers of breezedeus
24.4/25Track record — 49 public repos, account ~12 yr old
Inputs used
followers480
owner_typeUser
is_verified—
owner_loginbreezedeus
public_repos49
account_age_days4,595
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Engineering Quality

Are baseline engineering and documentation practices in place?

38Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

60Moderate
How it's scored
0/30README
25/25Documentation directory
15/15Documentation / homepage site — https://www.breezedeus.com/article/cnocr
0/10Repository description
10/10Topics — 5 topics
10/10Wiki
Inputs used
topicsocr, ocr-python, pytorch, chinese-character-recognition, english-character-recognition
has_wikiyes
homepagehttps://www.breezedeus.com/article/cnocr
docs_sitehttps://www.breezedeus.com/article/cnocr
has_readmeno
has_docs_diryes
has_descriptionno

Security

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

35Weak · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — branch protection not enabled on development/release branches
0/2.5CI-Tests — 0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0.8/7.5Code-Review — Found 2/11 approved changesets -- score normalized to 1
0.8/2.5Contributors — project has 1 contributing companies or organizations -- score normalized to 3
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 5 commit(s) and 1 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
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — Project has not signed or included provenance with any releases.
0/7.5Token-Permissions — no data
0/7.5Vulnerabilities — 185 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate1.8
Excluded from scoring (no data or not applicable): Dangerous-Workflow, Packaging, Token-Permissions. 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
advisories244
affected_packages19
assessed_packages95
unassessed_packages33
affected_by_severitycritical 5, high 7, moderate 6, unknown 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 95 resolved dependencies against OSV. 33 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.

50Moderate · 4% of overall
How it's scored
0/45Agent instructions — no CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
22.4/40Legible commit history — 42 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.42
agent_instruction_files—
agent_instruction_max_bytes—
How it's scored
18/18One-command bootstrap — Makefile
22/22Automated tests
0/11Lint / format config
0/11Static type checking
10/10Reproducible environment — Dockerfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
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_filesMakefile
has_devcontainerno
has_linter_configno
typecheck_configs—
agent_commit_share0
toolchain_manifests—
dependency_bot_commit_share0
How it's scored
0/45Type-checkable code — Python without a type-check config
55/55Manageable file sizes — 0/56 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes26,691
source_files_sampled56
oversized_source_files0
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

3,769GitHub stars
11contributors
15commits, last 12 months
76days since last push
37releases
1bus factor
53open issues
PyPIpackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 534 ⇿
0Stars
534Forks
37Releases

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.

0100200300400500600534122019-032022-112026-07
Major 2Minor 4Patch 12

Each point covers 7 days.

OpenSSF Scorecard 1.8 / 10
1.8aggregate

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 05:21 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
0CI-Tests0 out of 11 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
1Code-ReviewFound 2/11 approved changesets -- score normalized to 1
3Contributorsproject has 1 contributing companies or organizations -- score normalized to 3
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
5Maintained5 commit(s) and 1 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
0SASTSAST tool is not run on all commits -- score normalized to 0
0Security-Policysecurity policy file not detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
n/aToken-PermissionsNo tokens found
0Vulnerabilities185 existing vulnerabilities detected
All dependencies 128

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

RegistryPackageVersionRelation
PyPI0—indirect
PyPI1—indirect
PyPI2—indirect
PyPI3—indirect
PyPI4—indirect
PyPI5—indirect
PyPI6—indirect
PyPI7—indirect
PyPI8—indirect
PyPI9—indirect
PyPIaiohappyeyeballs2.4.3indirect
PyPIaiohttp3.11.8indirect
PyPIaiosignal1.3.1indirect
PyPIalbumentations—indirect
PyPIalbumentations1.3.1indirect
PyPIantlr4-python3-runtime4.9.3indirect
PyPIasync-timeout5.0.1indirect
PyPIattrs24.2.0indirect
PyPIcertifi2024.8.30indirect
PyPIcharset-normalizer3.4.0indirect
PyPIclick—indirect
PyPIclick8.1.7indirect
PyPIcnstd—indirect
PyPIcnstd1.2.8indirect
PyPIcoloredlogs15.0.1indirect
PyPIcolorlog6.9.0indirect
PyPIcontourpy1.3.0indirect
PyPIcycler0.12.1indirect
PyPIdatasets—indirect
PyPIdatasets3.1.0indirect
PyPIdill0.3.8indirect
PyPIdocker-pycreds0.4.0indirect
PyPIfastapi—indirect
PyPIfilelock3.16.1indirect
PyPIflatbuffers24.3.25indirect
PyPIfonttools4.55.0indirect
PyPIfrozenlist1.5.0indirect
PyPIfsspec2024.9.0indirect
PyPIgitdb4.0.11indirect
PyPIgitpython3.1.43indirect
PyPIhuggingface-hub0.26.3indirect
PyPIhumanfriendly10.0indirect
PyPIidna3.10indirect
PyPIimageio2.36.1indirect
PyPIjinja2—indirect
PyPIjinja23.1.4indirect
PyPIjoblib1.4.2indirect
PyPIkiwisolver1.4.7indirect
PyPIlazy-loader0.4indirect
PyPIlightning-utilities0.11.9indirect
PyPImarkupsafe3.0.2indirect
PyPImatplotlib3.9.3indirect
PyPImkdocs1.2.2indirect
PyPImkdocs-macros-plugin0.6.0indirect
PyPImkdocs-material7.3.0indirect
PyPImkdocs-material-extensions1.0.3indirect
PyPImkdocstrings0.16.1indirect
PyPImpmath1.3.0indirect
PyPImultidict6.1.0indirect
PyPImultiprocess0.70.16indirect
PyPInetworkx3.2.1indirect
PyPInumpy—indirect
PyPInumpy1.26.4indirect
PyPIomegaconf2.3.0indirect
PyPIonnx—indirect
PyPIonnx1.17.0indirect
PyPIonnxruntime—indirect
PyPIonnxruntime1.19.2indirect
PyPIonnxruntime-gpu—indirect
PyPIopencv-python4.10.0.84indirect
PyPIopencv-python-headless4.10.0.84indirect
PyPIpackaging24.2indirect
PyPIpandas2.2.3indirect
PyPIpillow—indirect
PyPIpillow11.0.0indirect
PyPIpip-tools—indirect
PyPIplatformdirs4.3.6indirect
PyPIpropcache0.2.0indirect
PyPIprotobuf5.29.0indirect
PyPIpsutil6.1.0indirect
PyPIpy-cpuinfo9.0.0indirect
PyPIpyarrow18.1.0indirect
PyPIpyclipper1.3.0.post6indirect
PyPIpydantic—indirect
PyPIpygments2.11indirect
PyPIpyparsing3.2.0indirect
PyPIpytest—indirect
PyPIpython-dateutil2.9.0.post0indirect
PyPIpython-multipart—indirect
PyPIpytorch-lightning—indirect
PyPIpytorch-lightning2.4.0indirect
PyPIpytz2024.2indirect
PyPIpyyaml6.0.2indirect
PyPIqudida0.0.4indirect
PyPIrapidocr—indirect
PyPIrapidocr3.9.1indirect
PyPIrequests2.32.3indirect
PyPIscikit-image0.24.0indirect
PyPIscikit-learn1.5.2indirect
PyPIscipy1.13.1indirect
PyPIseaborn0.13.2indirect
PyPIsentry-sdk2.19.0indirect
PyPIsetproctitle1.3.4indirect
PyPIshapely2.0.6indirect
PyPIsix1.16.0indirect
PyPIsmmap5.0.1indirect
PyPIsympy1.13.1indirect
PyPIthreadpoolctl3.5.0indirect
PyPItifffile2024.8.30indirect
PyPItorch—indirect
PyPItorch2.5.1indirect
PyPItorchmetrics—indirect
PyPItorchmetrics1.6.0indirect
PyPItorchvision—indirect
PyPItorchvision0.20.1indirect
PyPItqdm—indirect
PyPItqdm4.67.1indirect
PyPItyping-extensions4.12.2indirect
PyPItzdata2024.2indirect
PyPIultralytics8.3.39indirect
PyPIultralytics-thop2.0.12indirect
PyPIunidecode1.3.8indirect
PyPIurllib32.2.3indirect
PyPIuvicorn—indirect
PyPIwandb—indirect
PyPIwandb0.18.7indirect
PyPIxxhash3.5.0indirect
PyPIyarl1.18.0indirect
Dependency advisories 19

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

PackageVersionRelationSeverityAdvisoriesFixed in
aiohttp3.11.8indirectcritical663.14.3
gitpython3.1.43indirectcritical563.1.60
onnx1.17.0indirectcritical171.22.0
pillow11.0.0indirectcritical3412.3.0
torch2.5.1indirectcritical222.13.0
click8.1.7indirecthigh18.3.3
jinja23.1.4indirecthigh63.1.6
mkdocs1.2.2indirecthigh21.2.3
protobuf5.29.0indirecthigh46.33.5
pyarrow18.1.0indirecthigh223.0.1
pytorch-lightning2.4.0indirecthigh32.6.6
urllib32.2.3indirecthigh122.7.0
filelock3.16.1indirectmoderate43.20.3
fonttools4.55.0indirectmoderate24.60.2
idna3.10indirectmoderate23.15
mkdocs-material7.3.0indirectmoderate29.7.7
pygments2.11indirectmoderate42.20.0
requests2.32.3indirectmoderate42.33.0
datasets3.1.0indirectunknown15.0.1

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.