Public recordExcellent
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-17 13:12 UTC
cjermain / protoc-gen-pydantic
protoc plugin for Pydantic BaseModel
cjermain/protoc-gen-pydantic holds a health index of 81 out of 100, placing it in the Excellent band. It scores highest on Engineering Quality (96/100) and lowest on Community & Adoption (33/100). It was last updated 3 days ago. A single contributor accounts for most of its recent work.
81
overall / 100Software 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.
81
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)
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 69 is calibrated to 81 on the published index scale (record calibration 2026-08-02).
Ownership
Colin JermainPersonal account
25 followers47 public repossince May 2013
This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish |
|---|---|---|---|---|---|
| Go | github.com/cjermain/protoc-gen-pydantic | v0.18.0 | - | 22 | 30 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
85
Development activity
81Excellent
How it's scored
| 36/36 | Push recency — last push 3 days ago |
| 16.6/36 | Commit cadence — 24/52 weeks with commits |
| 18/18 | Commit volume — 363 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 363 |
| human_commit_share | 0.59 |
| days_since_last_push | 3 |
| active_weeks_last_year | 24 |
Release discipline
90Excellent
How it's scored
| 27/27 | Ships releases — 22 releases published |
| 36/36 | Release recency — latest release 30 days ago |
| 27/27 | Release cadence — a release every ~18 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — Project has not signed or included provenance with any releases. |
Inputs used
| releases_count | 22 |
| latest_release_tag | v0.18.0 |
| releases_from_tags | no |
| days_since_latest_release | 30 |
| mean_days_between_releases | 18 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
33
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 1 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 1 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
70Good
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 18/18 | CONTRIBUTING guide |
| 0/13.5 | Code of conduct |
| 0/7.2 | Issue template |
| 0/6.3 | PR template |
Inputs used
| has_readme | yes |
| has_license | yes |
| readme_badges | 11 |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | codecov.io, github.com, goreportcard.com, pkg.go.dev, shields.io |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
59
Maintainer resilience (bus factor)
22At Risk
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0.7/22.5 | Commit distribution — top contributor authored 97% of commits |
| 2.7/13.5 | Contributor breadth — 2 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 5 contributing companies or organizations |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 2 |
| top_contributor_share | 0.971 |
How it's scored
| 42/42 | Issue resolution — 100% of issues closed |
| 22/30 | PR acceptance — 104/142 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 0/15 | OpenSSF Scorecard: Code-Review — Found 0/2 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 104 |
| open_issues | 0 |
| closed_issues | 1 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 0 |
| prs_decided_30d | 0 |
| issue_closed_ratio | 1 |
| closed_unmerged_prs | 38 |
| first_time_authors_30d | 0 |
| first_time_prs_merged_30d | 0 |
| first_time_prs_decided_30d | 0 |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
56Moderate
How it's scored
| 10/30 | Ownership backing — personal (user) account |
| 0/20 | Verified domain — not applicable to user accounts |
| 10.2/25 | Owner reach — 25 followers of cjermain |
| 24.2/25 | Track record — 47 public repos, account ~13 yr old |
Inputs used
| followers | 25 |
| owner_type | User |
| is_verified | — |
| owner_login | cjermain |
| public_repos | 47 |
| account_age_days | 4,863 |
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 1 package(s) on go |
| 35/35 | Publish recency — latest publish 30 days ago |
| 20/20 | Version history — 22 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/cjermain/protoc-gen-pydantic |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 30 |
Engineering Quality
Are baseline engineering and documentation practices in place?
96
Engineering practices
94Exceptional
How it's scored
| 24/24 | CI workflows — 3 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .golangci.yml |
| 9.6/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | yes |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://cjermain.github.io/protoc-gen-pydantic/ |
| 10/10 | Repository description |
| 10/10 | Topics — 6 topics |
| 10/10 | Wiki |
Inputs used
| topics | protobuf, protoc, protocol-buffers, pydantic, pydantic-v2, protovalidate |
| has_wiki | yes |
| homepage | https://cjermain.github.io/protoc-gen-pydantic/ |
| docs_site | https://cjermain.github.io/protoc-gen-pydantic/ |
| has_readme | yes |
| has_docs_dir | yes |
| has_description | yes |
Security
Are visible security and supply-chain practices strong, without unresolved high-risk jurisdiction exposure?
69
Security posture
61Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — branch protection not enabled on development/release branches |
| 2.5/2.5 | CI-Tests — 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 0/7.5 | Code-Review — Found 0/2 approved changesets -- score normalized to 0 |
| 2.5/2.5 | Contributors — project has 5 contributing companies or organizations |
| 10/10 | Dangerous-Workflow — no dangerous workflow patterns detected |
| 7.5/7.5 | Dependency-Update-Tool — update tool detected |
| 0/5 | Fuzzing — project is not fuzzed |
| 2.5/2.5 | License — license file detected |
| 7.5/7.5 | Maintained — 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 5/5 | Packaging — packaging workflow detected |
| 0/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
| 5/5 | SAST — SAST tool is run on all commits |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — Project has not signed or included provenance with any releases. |
| 6.8/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 6.8/7.5 | Vulnerabilities — 1 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 18 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 0 |
| scorecard_aggregate | 6 |
Dependency advisories
100Exceptional
How it's scored
| 35/35 | Direct dependencies free of known advisories — no direct dependency carries a known advisory |
| 0/25 | Indirect dependencies free of known advisories — transitive set not separable from development and test dependencies in this scope |
| 0/40 | No advisories left outstanding — no advisory carries a publication date |
Inputs used
| source | osv |
| advisories | 1 |
| affected_packages | 1 |
| assessed_packages | 29 |
| unassessed_packages | 0 |
| affected_by_severity | unknown 1 |
| direct_affected_packages | 0 |
Excluded from scoring (no data or not applicable): Indirect dependencies free of known advisories, No advisories left outstanding. Remaining weights renormalized. Matched 29 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.
73
Agent context & guidance
100Exceptional
How it's scored
| 45/45 | Agent instructions — CLAUDE.md |
| 15/15 | Machine-readable docs (llms.txt) — llms.txt served by the project website (https://docs.pydantic.dev/llms.txt) |
| 40/40 | Legible commit history — 47 of 59 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | yes |
| llms_txt_url | https://docs.pydantic.dev/llms.txt |
| legible_history_share | 0.797 |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 24,212 |
How it's scored
| 18/18 | One-command bootstrap — .mise.toml, Justfile |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .golangci.yml |
| 0/11 | Static type checking |
| 10/10 | Reproducible environment — lockfile |
| 0/10 | Demonstrated agent practice — no agent-authored commits among the last 100 |
| 8/8 | Automated maintenance — 41 of the last 100 commits are automated dependency updates |
| 0/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum, uv.lock |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | .mise.toml, Justfile |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | go.mod |
| dependency_bot_commit_share | 0.41 |
Code legibility for models
53Moderate
How it's scored
| 0/45 | Type-checkable code — Python without a type-check config |
| 53.4/55 | Manageable file sizes — 3/106 source files over 60KB |
Inputs used
| primary_language | Python |
| largest_source_bytes | 122,292 |
| source_files_sampled | 106 |
| oversized_source_files | 3 |
Machine-readable interfaces
50Moderate
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — test/proto/api/v1/collections.proto, test/proto/api/v1/comments.proto, test/proto/api/v1/custom_options.proto, test/proto/api/v1/doc_comments.proto, test/proto/api/v1/enum_any_option.proto, test/proto/api/v1/enum_options.proto, test/proto/api/v1/enums.proto, test/proto/api/v1/field_types.proto, test/proto/api/v1/known_types.proto, test/proto/api/v1/messages.proto, test/proto/api/v1/nested_types.proto, test/proto/api/v1/oneofs.proto, test/proto/api/v1/reserved_names.proto, test/proto/api/v1/scalars.proto, test/proto/api/v1/self_reference.proto, test/proto/api/v1/validate.proto, test/proto/foo/bar/v1/cross_options.proto, test/proto/foo/bar/v1/cross_reference.proto, test/proto/partial/v1/validate_partial.proto |
| 0/20 | MCP server — not applicable to this kind of software |
| 0/40 | Runnable examples |
Inputs used
| example_dirs | — |
| has_mcp_signal | no |
| api_schema_files | test/proto/api/v1/collections.proto, test/proto/api/v1/comments.proto, test/proto/api/v1/custom_options.proto, test/proto/api/v1/doc_comments.proto, test/proto/api/v1/enum_any_option.proto, test/proto/api/v1/enum_options.proto, test/proto/api/v1/enums.proto, test/proto/api/v1/field_types.proto, test/proto/api/v1/known_types.proto, test/proto/api/v1/messages.proto, test/proto/api/v1/nested_types.proto, test/proto/api/v1/oneofs.proto, test/proto/api/v1/reserved_names.proto, test/proto/api/v1/scalars.proto, test/proto/api/v1/self_reference.proto, test/proto/api/v1/validate.proto, test/proto/foo/bar/v1/cross_options.proto, test/proto/foo/bar/v1/cross_reference.proto, test/proto/partial/v1/validate_partial.proto |
| interfaces_expected_of | — |
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.
Key facts
1GitHub stars
2contributors
363commits, last 12 months
3days since last push
22releases
1bus factor
0open issues
Go, PyPIpackage ecosystems
Data collection warnings
- Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token
More detail
OpenSSF Scorecard 6.0 / 10
6.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).
| 10 | Binary-Artifacts | no binaries found in the repo |
| 0 | Branch-Protection | branch protection not enabled on development/release branches |
| 10 | CI-Tests | 16 out of 16 merged PRs checked by a CI test -- score normalized to 10 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 0 | Code-Review | Found 0/2 approved changesets -- score normalized to 0 |
| 10 | Contributors | project has 5 contributing companies or organizations |
| 10 | Dangerous-Workflow | no dangerous workflow patterns detected |
| 10 | Dependency-Update-Tool | update tool detected |
| 0 | Fuzzing | project is not fuzzed |
| 10 | License | license file detected |
| 10 | Maintained | 30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10 |
| 10 | Packaging | packaging workflow detected |
| 0 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 0 |
| 10 | SAST | SAST tool is run on all commits |
| 0 | Security-Policy | security policy file not detected |
| 0 | Signed-Releases | Project has not signed or included provenance with any releases. |
| 9 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 9 | Vulnerabilities | 1 existing vulnerabilities detected |
Direct dependencies 2
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | google.golang.org/protobuf | v1.36.11 | go.mod |
| Go | github.com/google/cel-go | v0.31.0 | go.mod |
All dependencies 29
Full resolved dependency set from the GitHub dependency graph: 2 direct and 27 indirect (transitive) packages. The transitive closure is complete when the repository commits a lockfile.
| Registry | Package | Version | Relation |
|---|---|---|---|
| Go | github.com/google/cel-go | v0.31.0 | direct |
| Go | google.golang.org/protobuf | v1.36.11 | direct |
| Go | cel.dev/expr | v0.25.1 | indirect |
| Go | github.com/antlr4-go/antlr/v4 | v4.13.1 | indirect |
| Go | go.yaml.in/yaml/v3 | v3.0.4 | indirect |
| Go | golang.org/x/exp | v0.0.0-20240823005443-9b4947da3948 | indirect |
| Go | golang.org/x/text | v0.22.0 | indirect |
| Go | google.golang.org/genproto/googleapis/api | v0.0.0-20240826202546-f6391c0de4c7 | indirect |
| Go | google.golang.org/genproto/googleapis/rpc | v0.0.0-20240826202546-f6391c0de4c7 | indirect |
| PyPI | annotated-types | 0.7.0 | indirect |
| PyPI | colorama | 0.4.6 | indirect |
| PyPI | dnspython | 2.8.0 | indirect |
| PyPI | email-validator | 2.3.0 | indirect |
| PyPI | exceptiongroup | 1.3.1 | indirect |
| PyPI | idna | 3.15 | indirect |
| PyPI | iniconfig | 2.3.0 | indirect |
| PyPI | packaging | 26.0 | indirect |
| PyPI | pluggy | 1.6.0 | indirect |
| PyPI | protobuf | 7.35.1 | indirect |
| PyPI | pydantic | 2.13.4 | indirect |
| PyPI | pydantic-core | 2.46.4 | indirect |
| PyPI | pygments | 2.20.0 | indirect |
| PyPI | pytest | 9.1.1 | indirect |
| PyPI | ruff | 0.16.3 | indirect |
| PyPI | test | 0.1.0 | indirect |
| PyPI | tomli | 2.4.0 | indirect |
| PyPI | ty | 0.0.69 | indirect |
| PyPI | typing-extensions | 4.15.0 | indirect |
| PyPI | typing-inspection | 0.4.2 | indirect |
Dependency advisories 1
This repository publishes no package the index resolves, so its own dependency graph was assessed — 29 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.
| Package | Version | Relation | Severity | Advisories | Fixed in |
|---|---|---|---|---|---|
| golang.org/x/text | v0.22.0 | indirect | unknown | 1 | 0.39.0 |
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.
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 — Go.