Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-11-15 11:51 UTC

cloudfoundry / hydrator

GoApache-2.0★ 1 star⑂ 1 forksince Mar 2018View on GitHub ↗
KindCommand-line toolLibraryhow this is determined

cloudfoundry/hydrator holds a health index of 71 out of 100, placing it in the Good band. It scores highest on Vitality (98/100) and lowest on Community & Adoption (40/100). It was last updated 4 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

Cloud FoundryOrganization
766 followers575 public repossince Feb 2011

This repository is backed by an organization — shared, accountable stewardship that can outlive any single maintainer.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publish
Gocode.cloudfoundry.org/hydratorv0.113.0-1134 days ago

Metrics by category

Vitality

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

98Exceptional · 21% of overall
How it's scored
36/36Push recency — last push 4 days ago
35.3/36Commit cadence — 51/52 weeks with commits
15.5/18Commit volume — 52 commits in the last year
10/10OpenSSF Scorecard: Maintained — 14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year52
human_commit_share1
days_since_last_push4
active_weeks_last_year51

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 100 releases published
36/36Release recency — latest release 4 days ago
27/27Release cadence — a release every ~7 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count100
latest_release_tagv0.113.0
releases_from_tagsno
days_since_latest_release4
mean_days_between_releases7
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?

40Weak · 17% of overall
How it's scored
0/60Stars — 1 stars
0/25Forks — 1 forks
7.1/15Watchers — 20 watchers
Inputs used
forks1
stars1
watchers20
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
22.5/22.5README
22.5/22.5License — recognized license (Apache-2.0)
18/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
6.3/6.3PR template
Inputs used
has_readmeyes
has_licenseyes
readme_badges2
has_contributingyes
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgoreportcard.com, pkg.go.dev
has_pull_request_templateyes

Sustainability & Governance

Will the project survive its people — bus factor, responsiveness, who backs it, and package upkeep?

66Good · 23% of overall
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
3.2/22.5Commit distribution — top contributor authored 86% of commits
12.2/13.5Contributor breadth — 9 contributors
0/10OpenSSF Scorecard: Contributors — project has 0 contributing companies or organizations -- score normalized to 0
Inputs used
bus_factor1
contributors_sampled9
top_contributor_share0.86
How it's scored
42/42Issue resolution — 100% of issues closed
27.7/30PR acceptance — 12/13 decided PRs merged
0/13Newcomer PR acceptance — no first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-Review — Found 1/30 approved changesets -- score normalized to 0
Inputs used
merged_prs12
open_issues0
closed_issues2
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs1
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
30/30Ownership backing — organization-owned
0/20Verified domain
20.7/25Owner reach — 766 followers of cloudfoundry
25/25Track record — 575 public repos, account ~15 yr old
Inputs used
followers766
owner_typeOrganization
is_verifiedno
owner_logincloudfoundry
public_repos575
account_age_days5,750

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on go
35/35Publish recency — latest publish 4 days ago
20/20Version history — 113 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagescode.cloudfoundry.org/hydrator
ecosystemsgo
any_deprecatedno
min_days_since_publish4

Engineering Quality

Are baseline engineering and documentation practices in place?

44Weak · 19% of overall
How it's scored
0/24CI workflows
24/24Tests present
16/16Linter config — .flake8, .golangci.yaml, .golangci.yml
0/9.6Pre-commit hooks
6.4/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
Inputs used
has_cino
has_testsyes
has_editorconfigyes
has_linter_configyes
has_precommit_configno
How it's scored
30/30README
0/25Documentation directory
0/15Documentation / homepage site
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_site—
has_readmeyes
has_docs_dirno
has_descriptionno

Security

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

55Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0/7.5Branch-Protection — no data
0/2.5CI-Tests — 0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0/2.5CII-Best-Practices — no effort to earn an OpenSSF best practices badge detected
0/7.5Code-Review — Found 1/30 approved changesets -- score normalized to 0
0/2.5Contributors — project has 0 contributing companies or organizations -- score normalized to 0
0/10Dangerous-Workflow — no data
0/7.5Dependency-Update-Tool — no update tool detected
0/5Fuzzing — project is not fuzzed
2.5/2.5License — license file detected
7.5/7.5Maintained — 14 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
0/5Packaging — no data
0/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
5/5Security-Policy — security policy file detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — no data
7.5/7.5Vulnerabilities — 0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated13
scorecard_versionv5.5.0
checks_inconclusive5
scorecard_aggregate4.4
Excluded from scoring (no data or not applicable): Branch-Protection, Dangerous-Workflow, Packaging, Signed-Releases, Token-Permissions. Remaining weights renormalized.

Dependency advisories

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

77Good · 4% of overall
How it's scored
45/45Agent instructions — vendor/github.com/klauspost/compress/AGENTS.md, vendor/go.opentelemetry.io/otel/AGENTS.md
0/15Machine-readable docs (llms.txt)
40/40Legible commit history — 81 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.81
agent_instruction_filesvendor/github.com/klauspost/compress/AGENTS.md, vendor/go.opentelemetry.io/otel/AGENTS.md
agent_instruction_max_bytes7,134
How it's scored
18/18One-command bootstrap — vendor/github.com/Masterminds/semver/v3/Makefile, vendor/github.com/Microsoft/hcsshim/Makefile, vendor/github.com/go-task/slim-sprig/v3/Taskfile.yml, vendor/github.com/onsi/ginkgo/v2/Makefile, vendor/github.com/pkg/errors/Makefile, vendor/go.opentelemetry.io/otel/Makefile
22/22Automated tests
11/11Lint / format config — .flake8, .golangci.yaml, .golangci.yml
11/11Static type checking — Go (statically typed)
10/10Reproducible environment — lockfile
0/10Demonstrated agent practice — no agent-authored commits among the last 100
0/8Automated maintenance — no automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfilesgo.sum
has_dockerfileno
typed_languageyes
bootstrap_filesvendor/github.com/Masterminds/semver/v3/Makefile, vendor/github.com/Microsoft/hcsshim/Makefile, vendor/github.com/go-task/slim-sprig/v3/Taskfile.yml, vendor/github.com/onsi/ginkgo/v2/Makefile, vendor/github.com/pkg/errors/Makefile, vendor/go.opentelemetry.io/otel/Makefile
has_devcontainerno
has_linter_configyes
typecheck_configs—
agent_commit_share0
toolchain_manifestsgo.mod
dependency_bot_commit_share0
How it's scored
45/45Type-checkable code — Go (statically typed)
55/55Manageable file sizes — 0/33 source files over 60KB
Inputs used
primary_languageGo
largest_source_bytes19,705
source_files_sampled33
oversized_source_files0
How it's scored
40/40API schema (OpenAPI/GraphQL/proto) — vendor/github.com/containerd/cgroups/v3/cgroup1/stats/metrics.proto
0/20MCP server — not applicable to this kind of software
0/40Runnable examples
Inputs used
example_dirs—
has_mcp_signalno
api_schema_filesvendor/github.com/containerd/cgroups/v3/cgroup1/stats/metrics.proto
interfaces_expected_of—
Excluded from scoring (no data or not applicable): MCP server. Remaining weights renormalized.

Key facts

1GitHub stars
9contributors
52commits, last 12 months
4days since last push
100releases
1bus factor
0open issues
Gopackage ecosystems

Data collection warnings

  • Star history unavailable: GitHub GraphQL error: Resource not accessible by personal access token

More detail

OpenSSF Scorecard 4.4 / 10
4.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).Scorecard v5.5.0 · 2026-11-15 11:51 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
0CI-Tests0 out of 1 merged PRs checked by a CI test -- score normalized to 0
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 1/30 approved changesets -- score normalized to 0
0Contributorsproject has 0 contributing companies or organizations -- score normalized to 0
n/aDangerous-Workflowno workflows found
0Dependency-Update-Toolno update tool detected
0Fuzzingproject is not fuzzed
10Licenselicense file detected
10Maintained14 commit(s) and 0 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
10Security-Policysecurity policy file detected
n/aSigned-Releasesno releases found
n/aToken-PermissionsNo tokens found
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
Gocode.cloudfoundry.org/archiverv0.96.0go.mod
Gogithub.com/Microsoft/hcsshimv0.15.0go.mod
Gogithub.com/google/go-containerregistryv0.22.1go.mod
Gogithub.com/onsi/ginkgo/v2v2.34.0go.mod
Gogithub.com/onsi/gomegav1.44.0go.mod
Gogithub.com/opencontainers/go-digestv1.0.0go.mod
Gogithub.com/opencontainers/image-specv1.1.1go.mod
Gogithub.com/opencontainers/runtime-specv1.3.0go.mod
Gogithub.com/urfave/cliv1.22.17go.mod
All dependencies 39

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

RegistryPackageVersionRelation
Gocode.cloudfoundry.org/archiverv0.96.0direct
Gogithub.com/google/go-containerregistryv0.22.1direct
Gogithub.com/microsoft/hcsshimv0.15.0direct
Gogithub.com/onsi/ginkgo/v2v2.34.0direct
Gogithub.com/onsi/gomegav1.44.0direct
Gogithub.com/opencontainers/go-digestv1.0.0direct
Gogithub.com/opencontainers/image-specv1.1.1direct
Gogithub.com/opencontainers/runtime-specv1.3.0direct
Gogithub.com/urfave/cliv1.22.17direct
Gogithub.com/cespare/xxhash/v2v2.3.0indirect
Gogithub.com/containerd/cgroups/v3v3.1.3indirect
Gogithub.com/cpuguy83/go-md2man/v2v2.0.7indirect
Gogithub.com/cyphar/filepath-securejoinv0.7.0indirect
Gogithub.com/go-logr/logrv1.4.4indirect
Gogithub.com/go-logr/stdrv1.2.2indirect
Gogithub.com/go-task/slim-sprig/v3v3.0.0indirect
Gogithub.com/google/go-cmpv0.7.0indirect
Gogithub.com/google/pprofv0.0.0-20261110164715-8bb1ee682bd8indirect
Gogithub.com/google/uuidv1.6.0indirect
Gogithub.com/klauspost/compressv1.20.4indirect
Gogithub.com/masterminds/semver/v3v3.5.0indirect
Gogithub.com/microsoft/go-winiov0.6.4indirect
Gogithub.com/pkg/errorsv0.9.1indirect
Gogithub.com/russross/blackfriday/v2v2.1.0indirect
Gogithub.com/sirupsen/logrusv1.10.2indirect
Gogo.opentelemetry.io/auto/sdkv1.2.1indirect
Gogo.opentelemetry.io/otelv1.47.0indirect
Gogo.opentelemetry.io/otel/logv1.47.0indirect
Gogo.opentelemetry.io/otel/metricv1.47.0indirect
Gogo.opentelemetry.io/otel/sdkv1.47.0indirect
Gogo.opentelemetry.io/otel/tracev1.47.0indirect
Gogo.yaml.in/yaml/v3v3.0.6indirect
Gogolang.org/x/modv0.43.0indirect
Gogolang.org/x/netv0.62.0indirect
Gogolang.org/x/syncv0.25.0indirect
Gogolang.org/x/sysv0.50.0indirect
Gogolang.org/x/textv0.44.0indirect
Gogolang.org/x/toolsv0.52.0indirect
Gogoogle.golang.org/protobufv1.36.12indirect
Dependency advisories 0

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