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

bretttolbert / verbecc

Verbe Complete Conjugator (verbecc) supports Catalan, Spanish, French, Italian, Portuguese and Romanian and can predict conjugation for unknown verbs using Machine Learning

PythonLGPL-3.0★ 107 stars⑂ 15 forkssince Jul 2019View on GitHub ↗
KindLibraryCommand-line toolhow this is determined

bretttolbert/verbecc holds a health index of 75 out of 100, placing it in the Good band. It scores highest on Engineering Quality (90/100) and lowest on AI Readiness (33/100). It was last updated today. A single contributor accounts for most of its recent work.

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

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

Ownership

Brett TolbertPersonal account
0 followers27 public repossince Sep 2009

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

Package ecosystems

Metrics by category

Vitality

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

79Good · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
7.6/36Commit cadence11/52 weeks with commits
18/18Commit volume122 commits in the last year
10/10OpenSSF Scorecard: Maintained16 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year122
human_commit_share0.98
days_since_last_push0
active_weeks_last_year11
How it's scored
27/27Ships releases24 releases published
36/36Release recencylatest release 0 days ago
27/27Release cadencea release every ~35.1 days
0/10OpenSSF Scorecard: Signed-ReleasesProject has not signed or included provenance with any releases.
Inputs used
releases_count24
latest_release_tagv2.0.3
releases_from_tagsno
days_since_latest_release0
mean_days_between_releases35.1

Community & Adoption

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

50Moderate · 17% of overall
How it's scored
32.9/60Stars107 stars
9.6/25Forks15 forks
2.7/15Watchers4 watchers
Inputs used
forks15
stars107
watchers4
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5Licenserecognized license (LGPL-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_badges3
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno
How it's scored
47.7/80Monthly downloads3,789 downloads/month across pypi
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesverbecc
dependents
ecosystemspypi
total_downloads
monthly_downloads3,789
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?

51Moderate · 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
2.7/13.5Contributor breadth2 contributors
0/10OpenSSF Scorecard: Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled2
top_contributor_share0.998
How it's scored
24/42Issue resolution57% of issues closed
29/30PR acceptance29/30 decided PRs merged
13/13Newcomer PR acceptance1/1 first-time contributors' PRs merged in 30d
4.5/15OpenSSF Scorecard: Code-ReviewFound 2/6 approved changesets -- score normalized to 3
Inputs used
merged_prs29
open_issues9
closed_issues12
prs_merged_7d2
prs_decided_7d2
prs_merged_30d2
prs_decided_30d2
issue_closed_ratio0.571
closed_unmerged_prs1
first_time_authors_30d1
first_time_prs_merged_30d1
first_time_prs_decided_30d1
How it's scored
10/30Ownership backingpersonal (user) account
0/20Verified domainnot applicable to user accounts
0/25Owner reach0 followers of bretttolbert
22.5/25Track record27 public repos, account ~16 yr old
Inputs used
followers0
owner_typeUser
is_verified
owner_loginbretttolbert
public_repos27
account_age_days6,194
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 history73 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesverbecc
ecosystemspypi
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

90Excellent · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
16/16Linter configtox.ini
0/9.6Pre-commit hooks
0/6.4.editorconfig
20/20OpenSSF Scorecard: CI-Tests7 out of 7 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

100Exceptional
How it's scored
30/30README
25/25Documentation directory
15/15Documentation / homepage sitehttp://verbe.cc
10/10Repository description
10/10Topics20 topics
10/10Wiki
Inputs used
topicsconjugation, verbs, verb-conjugation, nlp, linguistics, french, spanish-language, french-language, portuguese-language, spanish-verbs, french-nlp, machine-learning, scikit-learn, natural-language-processing, portuguese-verbs, conjugator, romanian, romanian-language, catalan, catalan-language
has_wikiyes
homepagehttp://verbe.cc
docs_sitehttp://verbe.cc
has_readmeyes
has_docs_diryes
has_descriptionyes

Security

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

60Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
2.5/2.5CI-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
2.2/7.5Code-ReviewFound 2/6 approved changesets -- score normalized to 3
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
7.5/7.5Maintained16 commit(s) and 2 issue activity found in the last 90 days -- score normalized to 10
0/5Packagingno data
0/5Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
0/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-ReleasesProject has not signed or included provenance with any releases.
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate5
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging. Remaining weights renormalized.

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_packages17
unassessed_packages5
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 17 resolved dependencies against OSV. 5 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.

33At Risk · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
8.2/40Legible commit history15 of 98 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.153
agent_instruction_files
agent_instruction_max_bytes
How it's scored
0/18One-command bootstrap
22/22Automated tests
11/11Lint / format configtox.ini
0/11Static type checking
0/10Reproducible environment
2/10Demonstrated agent practice1 of the last 100 commits agent-authored or agent-credited
8/8Automated maintenance2 of the last 100 commits are automated dependency updates
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageno
bootstrap_files
has_devcontainerno
has_linter_configyes
typecheck_configs
agent_commit_share0.01
toolchain_manifests
dependency_bot_commit_share0.02
How it's scored
0/45Type-checkable codePython without a type-check config
54.3/55Manageable file sizes2/167 source files over 60KB
Inputs used
primary_languagePython
largest_source_bytes84,937
source_files_sampled167
oversized_source_files2

Key facts

107GitHub stars
2contributors
122commits, last 12 months
0days since last push
24releases
1bus factor
9open 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:verbecc@2.0.3; advisories assessed against the repository dependency graph instead

More detail

Star and fork history 0 ★ / 15 ⇿
0Stars
15Forks
23Releases

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.

03581013151512020-012023-042026-07
Major 1Minor 3Patch 19

Each point covers 6 days.

OpenSSF Scorecard 5.0 / 10
5.0aggregate

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 11:20 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-Tests7 out of 7 merged PRs checked by a CI test -- score normalized to 10
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
3Code-ReviewFound 2/6 approved changesets -- score normalized to 3
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
10Maintained16 commit(s) and 2 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
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.
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 16
RegistryPackageVersion constraintManifest
PyPIbackports.strenum(>=1.3.1,<2.0)pyproject.toml
PyPIcython>=3.1.4pyproject.toml
PyPIdataclass-wizard==0.35.1pyproject.toml
PyPIimportlib_resources==6.4.5pyproject.toml
PyPIimportlib_resources==6.5.2pyproject.toml
PyPIjsbeautifier>=1.15.4,<2.0pyproject.toml
PyPIlxml-stubs>=0.5.1pyproject.toml
PyPIlxml>=6.0.2pyproject.toml
PyPInumpy==1.26.2pyproject.toml
PyPInumpy==2.3.3pyproject.toml
PyPIpyaml==25.7.0pyproject.toml
PyPIscikit-learn==1.6.1pyproject.toml
PyPIscikit-learn==1.7.2pyproject.toml
PyPIscipy==1.13.1pyproject.toml
PyPIscipy==1.15.3pyproject.toml
PyPIscipy==1.16.2pyproject.toml
All dependencies 22

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

RegistryPackageVersionRelation
PyPIbackports-strenumdirect
PyPIcythondirect
PyPIcython3.1.4direct
PyPIdataclass-wizard0.35.1direct
PyPIimportlib-resources6.5.2direct
PyPIjsbeautifierdirect
PyPIjsbeautifier1.15.4direct
PyPIlxmldirect
PyPIlxml6.1.0direct
PyPIlxml-stubsdirect
PyPIlxml-stubs0.5.1direct
PyPInumpy2.3.3direct
PyPIpyaml25.7.0direct
PyPIscikit-learn1.7.2direct
PyPIscipy1.15.3direct
PyPIscipy1.16.2direct
PyPIiniconfig2.1.0indirect
PyPIjoblib1.4.2indirect
PyPIpackaging25.0indirect
PyPIpluggy1.6.0indirect
PyPIpytest9.0.3indirect
PyPIthreadpoolctl3.6.0indirect
Dependency advisories 0

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

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.