Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-26 08:45 UTC

xeonvs / open-code-review-toolkit

GitLab CI integration toolkit for Open Code Review

PythonApache-2.0★ 1 star⑂ 0 forkssince Jul 2026View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

xeonvs/open-code-review-toolkit holds a health index of 78 out of 100, placing it in the Good band. It scores highest on Engineering Quality (86/100) and lowest on Community & Adoption (47/100). It was last updated today. A single contributor accounts for most of its recent work.

78
overall / 100
Good

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.

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

Ownership

Max IrgiznovPersonal account
10 followers33 public repossince Mar 2015

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 publishTags
PyPIopen-code-review-toolkit0.8.32,646240 days agocicode-reviewgitlabopen-code-review

Metrics by category

Vitality

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

70Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
4.2/36Commit cadence6/52 weeks with commits
17/18Commit volume78 commits in the last year
0/10OpenSSF Scorecard: Maintainedproject was created within the last 90 days. Please review its contents carefully
Inputs used
commits_last_year78
human_commit_share0.975
days_since_last_push0
active_weeks_last_year6
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~1.3 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count24
latest_release_tagv0.8.3
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases1.3

Community & Adoption

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

47Weak · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

92Excellent
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
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_servicesapi.securityscorecards.dev, github.com, www.bestpractices.dev
has_pull_request_templateyes
How it's scored
45.6/80Monthly downloads2,646 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesopen-code-review-toolkit
dependents
ecosystemspypi
total_downloads
monthly_downloads2,646
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?

56Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
0/22.5Commit distributiontop contributor authored 100% of commits
1.4/13.5Contributor breadth1 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled1
top_contributor_share1
How it's scored
42/42Issue resolution100% of issues closed
30/30PR acceptance76/76 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs76
open_issues0
closed_issues68
prs_merged_7d13
prs_decided_7d13
prs_merged_30d59
prs_decided_30d59
issue_closed_ratio1
closed_unmerged_prs0
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 backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
7.5/25Owner reach10 followers of xeonvs
23.2/25Track record33 public repos, account ~11 yr old
Inputs used
followers10
owner_typeUser
is_verified
owner_loginxeonvs
public_repos33
account_age_days4,183
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on pypi
35/35Publish recencylatest publish 0 days ago
20/20Version history24 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesopen-code-review-toolkit
ecosystemspypi
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 workflows10 workflow(s)
24/24Tests present
16/16Linter configpyproject.toml ([tool.ruff])
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests30 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 sitehttps://pypi.org/project/open-code-review-toolkit/
10/10Repository description
10/10Topics5 topics
0/10Wiki
Inputs used
topicscode-review, devsecops, gitlab-ci, open-code-review, python
has_wikino
homepagehttps://pypi.org/project/open-code-review-toolkit/
docs_sitehttps://pypi.org/project/open-code-review-toolkit/
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

73Good · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
3/7.5Branch-Protectionbranch protection is not maximal on development and all release branches
2.5/2.5CI-Tests30 out of 30 merged PRs checked by a CI test -- score normalized to 10
1.2/2.5CII-Best-Practicesbadge detected: Passing
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0/2.5Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10/10Dangerous-Workflowno dangerous workflow patterns detected
7.5/7.5Dependency-Update-Toolupdate tool detected
0/5Fuzzingproject is not fuzzed
2.5/2.5Licenselicense file detected
0/7.5Maintainedproject was created within the last 90 days. Please review its contents carefully
5/5Packagingpackaging workflow detected
5/5Pinned-Dependenciesall dependencies are pinned
5/5SASTSAST tool is run on all commits
5/5Security-Policysecurity policy file detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated18
scorecard_versionv5.5.0
checks_inconclusive0
scorecard_aggregate6.6

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories0
affected_packages0
assessed_packages74
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 74 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.

81Excellent · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history72 of 78 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.923
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes5,195
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configpyproject.toml ([tool.ruff])
11/11Static type checkingsrc/ocr_toolkit/py.typed
10/10Reproducible environmentlockfile
0/10Demonstrated agent practiceno agent-authored commits among the last 80
8/8Automated maintenance2 of the last 80 commits are automated dependency updates
10/10OpenSSF Scorecard: Pinned-Dependenciesall dependencies are pinned
Inputs used
has_nixno
has_testsyes
lockfilesuv.lock
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configssrc/ocr_toolkit/py.typed
agent_commit_share0
toolchain_manifests
dependency_bot_commit_share0.025
How it's scored
27/45Type-checkable codePython with type-check config (src/ocr_toolkit/py.typed)
53/55Manageable file sizes6/168 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes206,436
source_files_sampled168
oversized_source_files6
How it's scored
0/40API schema (OpenAPI/GraphQL/proto)not applicable to this kind of software
0/20MCP servernot applicable to this kind of software
40/40Runnable examplesexamples
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

1GitHub stars
1contributors
78commits, last 12 months
0days since last push
24releases
1bus factor
0open issues
PyPIpackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
  • deps.dev does not index pypi:open-code-review-toolkit@0.8.3; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 6.6 / 10
6.6aggregate

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-08-26 08:44 UTC

10Binary-Artifactsno binaries found in the repo
4Branch-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
5CII-Best-Practicesbadge detected: Passing
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
10Dangerous-Workflowno dangerous workflow patterns detected
10Dependency-Update-Toolupdate tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
0Maintainedproject was created within the last 90 days. Please review its contents carefully
10Packagingpackaging workflow detected
10Pinned-Dependenciesall dependencies are pinned
10SASTSAST tool is run on all commits
10Security-Policysecurity policy file detected
0Signed-ReleasesProject has not signed or included provenance with any releases.
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
All dependencies 74

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

RegistryPackageVersionRelation
PyPIast-serialize0.6.0indirect
PyPIbandit1.9.4indirect
PyPIboolean-py5.0indirect
PyPIbuild1.5.0indirect
PyPIcachecontrol0.14.4indirect
PyPIcertifi2026.7.22indirect
PyPIcffi2.1.0indirect
PyPIcharset-normalizer3.4.9indirect
PyPIclick8.4.2indirect
PyPIcolorama0.4.6indirect
PyPIcoverage7.15.2indirect
PyPIcryptography50.0.0indirect
PyPIcyclonedx-python-lib11.11.0indirect
PyPIdefusedxml0.7.1indirect
PyPIdocutils0.23indirect
PyPIfilelock3.32.2indirect
PyPIhatch-vcs0.5.0indirect
PyPIhatchling1.31.0indirect
PyPIid1.6.1indirect
PyPIidna3.18indirect
PyPIiniconfig2.3.0indirect
PyPIjaraco-classes3.4.0indirect
PyPIjaraco-context6.1.2indirect
PyPIjaraco-functools4.6.0indirect
PyPIjeepney0.9.0indirect
PyPIjinja23.1.6indirect
PyPIkeyring25.7.0indirect
PyPIlibrt0.13.0indirect
PyPIlicense-expression30.4.4indirect
PyPImarkdown-it-py4.2.0indirect
PyPImarkupsafe3.0.3indirect
PyPImdurl0.1.2indirect
PyPImore-itertools11.1.0indirect
PyPImsgpack1.2.1indirect
PyPImypy2.3.0indirect
PyPImypy-extensions1.1.0indirect
PyPInh30.3.6indirect
PyPIpackageurl-python0.17.6indirect
PyPIpackaging26.2indirect
PyPIpathspec1.1.1indirect
PyPIpip26.2indirect
PyPIpip-api0.0.34indirect
PyPIpip-audit2.10.1indirect
PyPIpip-requirements-parser32.0.1indirect
PyPIplatformdirs4.11.0indirect
PyPIpluggy1.6.0indirect
PyPIpy-serializable2.1.0indirect
PyPIpycparser3.0indirect
PyPIpygments2.20.0indirect
PyPIpyparsing3.3.2indirect
PyPIpyproject-hooks1.2.0indirect
PyPIpytest9.1.1indirect
PyPIpytest-cov7.1.0indirect
PyPIpywin32-ctypes0.2.3indirect
PyPIpyyaml6.0.3indirect
PyPIreadme-renderer45.0indirect
PyPIrequests2.34.2indirect
PyPIrequests-toolbelt1.0.0indirect
PyPIrfc39862.0.0indirect
PyPIrich15.0.0indirect
PyPIruff0.16.0indirect
PyPIsecretstorage3.5.0indirect
PyPIsetuptools83.0.0indirect
PyPIsetuptools-scm10.2.1indirect
PyPIsortedcontainers2.4.0indirect
PyPIstevedore5.9.0indirect
PyPItomli2.4.1indirect
PyPItomli-w1.2.0indirect
PyPItowncrier25.8.0indirect
PyPItrove-classifiers2026.6.1.19indirect
PyPItwine7.0.0indirect
PyPItyping-extensions4.16.0indirect
PyPIurllib32.7.0indirect
PyPIvcs-versioning2.2.3indirect
Dependency advisories 0

This repository publishes no package the index resolves, so its own dependency graph was assessed — 74 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 statisticsPyPI.