Public recordExceptional
Software health reportschema 0.12.0 · metrics 2.10.0 · 2026-07-18 10:34 UTC
stacklok / toolhive-registry-server
Discover, govern and control access to MCP servers and agent skills across your organization
stacklok/toolhive-registry-server holds a health index of 95 out of 100, placing it in the Exceptional band. It scores highest on Vitality (94/100) and lowest on Community & Adoption (56/100). It was last updated today. 2 contributors account for most of its recent work.
95
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.
95
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 82 is calibrated to 95 on the published index scale (record calibration 2026-08-02).
Ownership
StacklokOrganization
288 followers46 public repossince Jul 2022
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 |
|---|---|---|---|---|---|
| Go | github.com/stacklok/toolhive-registry-server | v1.5.0 | - | 56 | 0 days ago |
Metrics by category
Vitality
Is the project alive — is code being written and are releases shipping?
94
Development activity
92Excellent
How it's scored
| 36/36 | Push recency — last push 0 days ago |
| 27.7/36 | Commit cadence — 40/52 weeks with commits |
| 18/18 | Commit volume — 628 commits in the last year |
| 10/10 | OpenSSF Scorecard: Maintained — 30 commit(s) and 7 issue activity found in the last 90 days -- score normalized to 10 |
Inputs used
| commits_last_year | 628 |
| human_commit_share | — |
| days_since_last_push | 0 |
| active_weeks_last_year | 40 |
Release discipline
98Exceptional
How it's scored
| 27/27 | Ships releases — 55 releases published |
| 36/36 | Release recency — latest release 0 days ago |
| 27/27 | Release cadence — a release every ~6.4 days |
| 8/10 | OpenSSF Scorecard: Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
Inputs used
| releases_count | 55 |
| latest_release_tag | v1.5.0 |
| releases_from_tags | no |
| days_since_latest_release | 0 |
| mean_days_between_releases | 6.4 |
Community & Adoption
Does the project have users, downloads, attention, and a welcoming setup for contributors?
56
Popularity & adoption
30At Risk
How it's scored
| 20.7/60 | Stars — 20 stars |
| 9/25 | Forks — 13 forks |
| 0/15 | Watchers — 2 watchers |
Inputs used
| forks | 13 |
| stars | 20 |
| watchers | 2 |
| growth_state | unverified |
| growth_factor_pct | 100 |
| growth_unverified_reason | no_history |
Community health
85Excellent
How it's scored
| 22.5/22.5 | README |
| 22.5/22.5 | License — recognized license (Apache-2.0) |
| 18/18 | CONTRIBUTING guide |
| 13.5/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 | — |
| has_contributing | yes |
| has_issue_template | no |
| has_code_of_conduct | yes |
| readme_badge_services | — |
| has_pull_request_template | no |
Sustainability & Governance
Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?
83
Maintainer resilience (bus factor)
62Moderate
How it's scored
| 25.2/54 | Bus factor — 2 contributor(s) cover half of all commits |
| 13.6/22.5 | Commit distribution — top contributor authored 40% of commits |
| 13.5/13.5 | Contributor breadth — 21 contributors |
| 10/10 | OpenSSF Scorecard: Contributors — project has 8 contributing companies or organizations |
Inputs used
| bus_factor | 2 |
| contributors_sampled | 21 |
| top_contributor_share | 0.396 |
Issue & PR responsiveness
92Excellent
How it's scored
| 37.2/42 | Issue resolution — 89% of issues closed |
| 27.5/30 | PR acceptance — 639/698 decided PRs merged |
| 0/13 | Newcomer PR acceptance — no first-time contributor's PR decided in 30d |
| 15/15 | OpenSSF Scorecard: Code-Review — all changesets reviewed |
Inputs used
| merged_prs | 639 |
| open_issues | 17 |
| closed_issues | 132 |
| prs_merged_7d | — |
| prs_decided_7d | — |
| prs_merged_30d | — |
| prs_decided_30d | — |
| issue_closed_ratio | 0.886 |
| closed_unmerged_prs | 59 |
| first_time_authors_30d | — |
| first_time_prs_merged_30d | — |
| first_time_prs_decided_30d | — |
Excluded from scoring (no data or not applicable): Newcomer PR acceptance. Remaining weights renormalized.
Ownership & stewardship
85Excellent
How it's scored
| 30/30 | Ownership backing — organization-owned |
| 0/20 | Verified domain — verified-domain status not read for this organization |
| 17.7/25 | Owner reach — 288 followers of stacklok |
| 20.1/25 | Track record — 46 public repos, account ~3 yr old |
Inputs used
| followers | 288 |
| owner_type | Organization |
| is_verified | — |
| owner_login | stacklok |
| public_repos | 46 |
| account_age_days | 1,449 |
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 0 days ago |
| 20/20 | Version history — 56 published versions |
| 20/20 | Not deprecated — active, not deprecated or yanked |
Inputs used
| packages | github.com/stacklok/toolhive-registry-server |
| ecosystems | go |
| any_deprecated | no |
| min_days_since_publish | 0 |
Engineering Quality
Are baseline engineering and documentation practices in place?
89
Engineering practices
82Excellent
How it's scored
| 24/24 | CI workflows — 16 workflow(s) |
| 24/24 | Tests present |
| 16/16 | Linter config — .golangci.yml |
| 0/9.6 | Pre-commit hooks |
| 0/6.4 | .editorconfig |
| 18/20 | OpenSSF Scorecard: CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9 |
Inputs used
| has_ci | yes |
| has_tests | yes |
| has_editorconfig | no |
| has_linter_config | yes |
| has_precommit_config | no |
Documentation
100Exceptional
How it's scored
| 30/30 | README |
| 25/25 | Documentation directory |
| 15/15 | Documentation / homepage site — https://docs.stacklok.com/toolhive/guides-registry/ |
| 10/10 | Repository description |
| 10/10 | Topics — 13 topics |
| 10/10 | Wiki |
Inputs used
| topics | ai, ai-governance, ai-security, golang, governance, mcp, mcp-registry, mcp-security, mcp-servers, mcp-tools, model-context-protocol, registry, security |
| has_wiki | yes |
| homepage | https://docs.stacklok.com/toolhive/guides-registry/ |
| docs_site | https://docs.stacklok.com/toolhive/guides-registry/ |
| 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?
81
Security posture
81Excellent
How it's scored
| 7.5/7.5 | Binary-Artifacts — no binaries found in the repo |
| 6/7.5 | Branch-Protection — branch protection is not maximal on development and all release branches |
| 2.2/2.5 | CI-Tests — 27 out of 30 merged PRs checked by a CI test -- score normalized to 9 |
| 0/2.5 | CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected |
| 7.5/7.5 | Code-Review — all changesets reviewed |
| 2.5/2.5 | Contributors — project has 8 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 7 issue activity found in the last 90 days -- score normalized to 10 |
| 5/5 | Packaging — packaging workflow detected |
| 4.5/5 | Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9 |
| 5/5 | SAST — SAST tool is run on all commits |
| 5/5 | Security-Policy — security policy file detected |
| 6/7.5 | Signed-Releases — 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 0/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 | 8.1 |
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.
92
Agent context & guidance
75Good
How it's scored
| 45/45 | Agent instructions — CLAUDE.md |
| 0/15 | Machine-readable docs (llms.txt) |
| 0/40 | Legible commit history — no data |
Inputs used
| has_llms_txt | no |
| llms_txt_url | — |
| legible_history_share | — |
| agent_instruction_files | CLAUDE.md |
| agent_instruction_max_bytes | 10,767 |
Excluded from scoring (no data or not applicable): Legible commit history. Remaining weights renormalized.
Verify loop (build / test / typecheck)
99Exceptional
How it's scored
| 18/18 | One-command bootstrap — Taskfile.yml |
| 22/22 | Automated tests |
| 11/11 | Lint / format config — .golangci.yml |
| 11/11 | Static type checking — Go (statically typed) |
| 10/10 | Reproducible environment — Dockerfile, lockfile |
| 0/10 | Demonstrated agent practice — no data |
| 0/8 | Automated maintenance — no data |
| 9/10 | OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 9 |
Inputs used
| has_nix | no |
| has_tests | yes |
| lockfiles | go.sum |
| has_dockerfile | yes |
| typed_language | yes |
| bootstrap_files | Taskfile.yml |
| has_devcontainer | no |
| has_linter_config | yes |
| typecheck_configs | — |
| agent_commit_share | — |
| toolchain_manifests | — |
| dependency_bot_commit_share | — |
Excluded from scoring (no data or not applicable): Demonstrated agent practice, Automated maintenance. Remaining weights renormalized.
Code legibility for models
99Exceptional
How it's scored
| 45/45 | Type-checkable code — Go (statically typed) |
| 53.6/55 | Manageable file sizes — 6/243 source files over 60KB |
Inputs used
| primary_language | Go |
| largest_source_bytes | 127,447 |
| source_files_sampled | 243 |
| oversized_source_files | 6 |
Machine-readable interfaces
100Exceptional
How it's scored
| 40/40 | API schema (OpenAPI/GraphQL/proto) — docs/thv-registry-api/swagger.json, docs/thv-registry-api/swagger.yaml |
| 20/20 | MCP server |
| 40/40 | Runnable examples — examples |
Inputs used
| example_dirs | examples |
| has_mcp_signal | yes |
| api_schema_files | docs/thv-registry-api/swagger.json, docs/thv-registry-api/swagger.yaml |
| interfaces_expected_of | — |
Key facts
20GitHub stars
21contributors
628commits, last 12 months
0days since last push
55releases
2bus factor
17open issues
Gopackage ecosystems
Data collection warnings
- GitHub dependency-graph SBOM unavailable (404); the dependency graph may be disabled for this repository
More detail
OpenSSF Scorecard 8.1 / 10
8.1aggregate
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 |
| 8 | Branch-Protection | branch protection is not maximal on development and all release branches |
| 9 | CI-Tests | 27 out of 30 merged PRs checked by a CI test -- score normalized to 9 |
| 0 | CII-Best-Practices | no effort to earn an OpenSSF best practices badge detected |
| 10 | Code-Review | all changesets reviewed |
| 10 | Contributors | project has 8 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 7 issue activity found in the last 90 days -- score normalized to 10 |
| 10 | Packaging | packaging workflow detected |
| 9 | Pinned-Dependencies | dependency not pinned by hash detected -- score normalized to 9 |
| 10 | SAST | SAST tool is run on all commits |
| 10 | Security-Policy | security policy file detected |
| 8 | Signed-Releases | 5 out of the last 5 releases have a total of 5 signed artifacts. |
| 0 | Token-Permissions | detected GitHub workflow tokens with excessive permissions |
| 9 | Vulnerabilities | 1 existing vulnerabilities detected |
Direct dependencies 33
| Registry | Package | Version constraint | Manifest |
|---|---|---|---|
| Go | github.com/Masterminds/semver/v3 | v3.5.0 | go.mod |
| Go | github.com/aws/smithy-go | v1.27.3 | go.mod |
| Go | github.com/go-chi/chi/v5 | v5.3.0 | go.mod |
| Go | github.com/go-git/go-billy/v5 | v5.9.0 | go.mod |
| Go | github.com/go-git/go-git/v5 | v5.19.1 | go.mod |
| Go | github.com/go-logr/logr | v1.4.3 | go.mod |
| Go | github.com/gobwas/glob | v0.2.3 | go.mod |
| Go | github.com/golang-jwt/jwt/v5 | v5.3.1 | go.mod |
| Go | github.com/golang-migrate/migrate/v4 | v4.19.1 | go.mod |
| Go | github.com/google/uuid | v1.6.0 | go.mod |
| Go | github.com/jackc/pgpassfile | v1.0.0 | go.mod |
| Go | github.com/jackc/pgx/v5 | v5.10.0 | go.mod |
| Go | github.com/modelcontextprotocol/registry | v1.8.0 | go.mod |
| Go | github.com/spf13/cobra | v1.10.2 | go.mod |
| Go | github.com/spf13/viper | v1.21.0 | go.mod |
| Go | github.com/stacklok/toolhive | v0.33.0 | go.mod |
| Go | github.com/stacklok/toolhive-core | v0.0.28 | go.mod |
| Go | github.com/stretchr/testify | v1.11.1 | go.mod |
| Go | github.com/swaggo/swag/v2 | v2.0.0-rc5 | go.mod |
| Go | github.com/testcontainers/testcontainers-go | v0.43.0 | go.mod |
| Go | github.com/testcontainers/testcontainers-go/modules/postgres | v0.43.0 | go.mod |
| Go | go.opentelemetry.io/otel | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/metric | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/sdk | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/sdk/metric | v1.44.0 | go.mod |
| Go | go.opentelemetry.io/otel/trace | v1.44.0 | go.mod |
| Go | go.uber.org/mock | v0.6.0 | go.mod |
| Go | golang.org/x/term | v0.45.0 | go.mod |
| Go | gopkg.in/yaml.v3 | v3.0.1 | go.mod |
| Go | k8s.io/apimachinery | v0.36.2 | go.mod |
| Go | sigs.k8s.io/controller-runtime | v0.24.1 | go.mod |
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.12.0 — full methodology · metrics wiki.
How one result sits in the wider record: aggregate statistics — Go.