Public recordGood
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-09-15 21:07 UTC
pidgr / pidgr-proto
Pidgr protobuf messages repo
pidgr/pidgr-proto holds a health index of 67 out of 100, placing it in the Good band. It scores highest on Vitality (90/100) and lowest on Community & Adoption (32/100). It was last updated 1 day ago. A single contributor accounts for most of its recent work.
67
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.
67
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 61 is calibrated to 67 on the published index scale (record calibration 2026-08-02).
Ownership
PidgrOrganization
1 follower2 public repossince Feb 2018
This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.
Package ecosystems
| Registry | Package | Version | Downloads / mo | Versions | Last publish | Tags |
|---|---|---|---|---|---|---|
| Go | github.com/pidgr/pidgr-proto/gen/go | v0.106.0 | - | 108 | 21 days ago | — |
| crates.io | pidgr-proto | 0.106.0 | 225 | 69 | 21 days ago | codegenprotobufgrpctonicpidgrapi-bindings |
| npm | @pidgr/proto | 0.106.0 | 1,978 | 75 | 21 days ago | pidgrprotobufgrpcconnectinternal-communicationscampaignsrpccodegen |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
90
Development activity
84Excellent
How it's scored
| 36/36 | Push recency — last push 1 days ago |
| 20.1/36 | Commit cadence — 29/52 weeks with commits |
| 18/18 | Commit volume — 291 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 | 291 |
| human_commit_share | 0.75 |
| days_since_last_push | 1 |
| active_weeks_last_year | 29 |
Release discipline
100Exceptional
How it's scored
| 27/27 | Ships releases — 100 releases published |
| 36/36 | Release recency — latest release 21 days ago |
| 27/27 | Release cadence — a release every ~0.6 days |
| 0/10 | OpenSSF Scorecard: Signed-Releases — no data |
Inputs used
| releases_count | 100 |
| latest_release_tag | v0.106.0 |
| releases_from_tags | no |
| days_since_latest_release | 21 |
| mean_days_between_releases | 0.6 |
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?
32
Popularity & adoption
1Critical
How it's scored
| 0/60 | Stars — 0 stars |
| 0/25 | Forks — 0 forks |
| 0/15 | Watchers — 0 watchers |
Inputs used
| forks | 0 |
| stars | 0 |
| watchers | 0 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
50Moderate
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 0/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 | 7 |
| has_contributing | no |
| has_issue_template | no |
| has_code_of_conduct | no |
| readme_badge_services | github.com, pkg.go.dev, shields.io |
| has_pull_request_template | no |
Ecosystem adoption (downloads)
56Moderate
How it's scored
| 44.6/80 | Monthly downloads — 2,203 downloads/month across crates, go, npm |
| 0/20 | Registry dependents — not reported by this ecosystem |
Inputs used
| packages | github.com/pidgr/pidgr-proto/gen/go, pidgr-proto, @pidgr/proto |
| dependents | — |
| ecosystems | crates, go, npm |
| total_downloads | 1,419 |
| monthly_downloads | 2,203 |
| 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?
51
Maintainer resilience (bus factor)
10Critical
How it's scored
| 9/54 | Bus factor — 1 contributor(s) cover half of all commits |
| 0/22.5 | Commit distribution — top contributor authored 100% of commits |
| 1.4/13.5 | Contributor breadth — 1 contributors |
| 0/10 | OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
Inputs used
| bus_factor | 1 |
| contributors_sampled | 1 |
| top_contributor_share | 1 |
How it's scored
| 0/42 | Issue resolution — no issues or no data |
| 29.3/30 | PR acceptance — 243/249 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/22 approved changesets -- score normalized to 0 |
Inputs used
| merged_prs | 243 |
| open_issues | 0 |
| closed_issues | 0 |
| prs_merged_7d | 0 |
| prs_decided_7d | 0 |
| prs_merged_30d | 20 |
| prs_decided_30d | 20 |
| issue_closed_ratio | — |
| closed_unmerged_prs | 6 |
| 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): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
48Weak
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain |
| 2.2/25 | Owner reach — 1 followers of pidgr |
| 15.5/25 | Track record — 2 public repos, account ~8 yr old |
Inputs used
| followers | 1 |
| owner_type | Organization |
| is_verified | no |
| owner_login | pidgr |
| public_repos | 2 |
| account_age_days | 3,141 |
Package maintenance
100Exceptional
How it's scored
| 25/25 | Published & resolvable — 3 package(s) on crates, go, npm |
| 35/35 | Publish recency — latest publish 21 days ago |
| 20/20 | Version history — 108 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/pidgr/pidgr-proto/gen/go, pidgr-proto, @pidgr/proto |
| ecosystems | crates, go, npm |
| any_deprecated | no |
| min_days_since_publish | 21 |
Engineering Quality
Are baseline engineering and documentation practices in place?
73
Engineering practices
68Good
How it's scored
| 24/24 | CI workflows — 3 workflow(s) |
| 24/24 | Tests present |
| 0/16 | Linter config |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 20/20 | OpenSSF Scorecard: CI-Tests — 30 out of 30 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 | no |
| has_precommit_config | no |
Documentation
80Excellent
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://docs.rs/pidgr-proto |
| 10/10 | Repository description |
| 0/10 | Topics |
| 0/10 | Wiki |
Inputs used
| topics | — |
| has_wiki | no |
| homepage | — |
| docs_site | https://docs.rs/pidgr-proto |
| 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?
54
Security posture
54Moderate
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 0/7.5 | Branch-Protection — no data |
| 2.5/2.5 | CI-Tests — 30 out of 30 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/22 approved changesets -- score normalized to 0 |
| 0/2.5 | Contributors — project has 0 contributing companies or organizations -- score normalized to 0 |
| 0/10 | Dangerous-Workflow — 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 |
| 5/5 | Pinned-Dependencies — all dependencies are pinned |
| 5/5 | SAST — SAST tool is run on all commits |
| 0/5 | Security-Policy — security policy file not detected |
| 0/7.5 | Signed-Releases — no data |
| 0/7.5 | Token-Permissions — detected GitHub workflow tokens with excessive permissions |
| 6/7.5 | Vulnerabilities — 2 existing vulnerabilities detected |
Inputs used
| source | openssf_scorecard |
| checks_evaluated | 16 |
| scorecard_version | v5.5.0 |
| checks_inconclusive | 2 |
| scorecard_aggregate | 5.4 |
Excluded from scoring (no data or not applicable): Branch-Protection, Signed-Releases. Remaining weights renormalized.
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.
72
Agent context & guidance
85Excellent
How it's scored
| 45/45 | Agent instructions — CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 40/40 | Legible commit history — 75 of 75 human commits state their intent (structured subject or explanatory body) |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | 1 |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 4,806 |
Verify loop (build / test / typecheck)
63Moderate
How it's scored
| 12.6/18 | One-command bootstrap — gen/go/go.mod, gen/rust/Cargo.toml (toolchain convention, no task runner) |
| 22/22 | Automated tests |
| 0/11 | Lint / format config |
| 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 — 24 of the last 100 commits are automated dependency updates |
| 10/10 | OpenSSF Scorecard: Pinned-Dependencies — all dependencies are pinned |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | Cargo.lock, go.sum, package-lock.json |
| has_dockerfile | no |
| typed_language | no |
| bootstrap_files | — |
| has_devcontainer | no |
| has_linter_config | no |
| typecheck_configs | — |
| agent_commit_share | 0 |
| toolchain_manifests | gen/go/go.mod, gen/rust/Cargo.toml |
| dependency_bot_commit_share | 0.24 |
Code legibility for models
89Excellent
How it's scored
| 0/45 | Type-checkable code — primary language unknown |
| 49.2/55 | Manageable file sizes — 12/113 source files over 60KB |
Inputs used
| primary_language | — |
| largest_source_bytes | 888,106 |
| source_files_sampled | 113 |
| oversized_source_files | 12 |
Excluded from scoring (no data or not applicable): Type-checkable code. Remaining weights renormalized.
Machine-readable interfaces
50Moderate
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — proto/pidgr/v1/action.proto, proto/pidgr/v1/api_key.proto, proto/pidgr/v1/audit.proto, proto/pidgr/v1/authorization.proto, proto/pidgr/v1/campaign.proto, proto/pidgr/v1/channel_events.proto, proto/pidgr/v1/common.proto, proto/pidgr/v1/device.proto, proto/pidgr/v1/group.proto, proto/pidgr/v1/heatmap.proto, proto/pidgr/v1/inbox.proto, proto/pidgr/v1/insights.proto, proto/pidgr/v1/integrations.proto, proto/pidgr/v1/integrations_service.proto, proto/pidgr/v1/invite_link.proto, proto/pidgr/v1/member.proto, proto/pidgr/v1/objectives.proto, proto/pidgr/v1/org_security_keys_service.proto, proto/pidgr/v1/organization.proto, proto/pidgr/v1/privacy.proto, proto/pidgr/v1/render.proto, proto/pidgr/v1/replay.proto, proto/pidgr/v1/role.proto, proto/pidgr/v1/sso.proto, proto/pidgr/v1/team.proto, proto/pidgr/v1/template.proto, proto/pidgr/v1/token.proto, proto/pidgr/v1/user.proto, proto/pidgr/v1/verification.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 | proto/pidgr/v1/action.proto, proto/pidgr/v1/api_key.proto, proto/pidgr/v1/audit.proto, proto/pidgr/v1/authorization.proto, proto/pidgr/v1/campaign.proto, proto/pidgr/v1/channel_events.proto, proto/pidgr/v1/common.proto, proto/pidgr/v1/device.proto, proto/pidgr/v1/group.proto, proto/pidgr/v1/heatmap.proto, proto/pidgr/v1/inbox.proto, proto/pidgr/v1/insights.proto, proto/pidgr/v1/integrations.proto, proto/pidgr/v1/integrations_service.proto, proto/pidgr/v1/invite_link.proto, proto/pidgr/v1/member.proto, proto/pidgr/v1/objectives.proto, proto/pidgr/v1/org_security_keys_service.proto, proto/pidgr/v1/organization.proto, proto/pidgr/v1/privacy.proto, proto/pidgr/v1/render.proto, proto/pidgr/v1/replay.proto, proto/pidgr/v1/role.proto, proto/pidgr/v1/sso.proto, proto/pidgr/v1/team.proto, proto/pidgr/v1/template.proto, proto/pidgr/v1/token.proto, proto/pidgr/v1/user.proto, proto/pidgr/v1/verification.proto |
| interfaces_expected_of | — |
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.
Key facts
0GitHub stars
1contributors
291commits, last 12 months
1days since last push
100releases
1bus factor
0open issues
—package ecosystems
Data collection warnings
- Language breakdown unavailable
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 5.4 / 10
5.4aggregate
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 |
| n/a | Branch-Protection | internal 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 |
| 10 | CI-Tests | 30 out of 30 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/22 approved changesets -- score normalized to 0 |
| 0 | Contributors | project has 0 contributing companies or organizations -- score normalized to 0 |
| 0 | Dangerous-Workflow | 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 |
| 10 | Pinned-Dependencies | all dependencies are pinned |
| 10 | SAST | SAST tool is run on all commits |
| 0 | Security-Policy | security policy file not detected |
| n/a | Signed-Releases | no releases found |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 8 | Vulnerabilities | 2 existing vulnerabilities detected |
Direct dependencies 9
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | connectrpc.com/connect | v1.20.0 | gen/go/go.mod |
| Go | google.golang.org/grpc | v1.83.2 | gen/go/go.mod |
| Go | google.golang.org/protobuf | v1.36.12 | gen/go/go.mod |
| crates.io | prost | 0.14 | gen/rust/Cargo.toml |
| crates.io | prost-types | 0.14 | gen/rust/Cargo.toml |
| crates.io | tonic | 0.14 | gen/rust/Cargo.toml |
| crates.io | tonic-prost | 0.14 | gen/rust/Cargo.toml |
| npm | @bufbuild/protobuf | ^2.0.0 | gen/ts/package.json |
| npm | @connectrpc/connect | ^2.0.0 | gen/ts/package.json |
All dependencies not collected
The resolved dependency set could not be collected for this report: GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
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, crates.io, npm.