Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-08-30 06:54 UTC

hydro-project / trybuild

Test harness for ui tests of compiler diagnostics

RustApache-2.0★ 0 stars⑂ 0 forkssince Dec 2022forkView on GitHub ↗

hydro-project/trybuild holds a health index of 39 out of 100, placing it in the Weak band. It scores highest on Security (56/100) and lowest on Community & Adoption (25/100). It was last updated 5 days ago. A single contributor accounts for most of its recent work.

39
overall / 100
Weak

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.

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

Ownership

HydroOrganization
155 followers70 public repossince Jul 2018

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.iotrybuild-internals-api1.0.1207,11235 days agodev-dependenciesmacrostesting

Metrics by category

Vitality

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

44Weak · 21% of overall
How it's scored
36/36Push recencylast push 5 days ago
11.8/36Commit cadence17/52 weeks with commits
15.6/18Commit volume54 commits in the last year
10/10OpenSSF Scorecard: Maintained26 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year54
human_commit_share1
days_since_last_push5
active_weeks_last_year17
How it's scored
0/27Ships releasesno releases published
0/36Release recencyno releases
0/27Release cadenceno releases
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count0
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?

25At Risk · 17% of overall
How it's scored
0/60Stars0 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars0
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history
How it's scored
0/22.5README
22.5/22.5Licenserecognized license (Apache-2.0)
0/18CONTRIBUTING guide
0/13.5Code of conduct
0/7.2Issue template
0/6.3PR template
Inputs used
has_readmeno
has_licenseno
readme_badges4
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesshields.io
has_pull_request_templateno
How it's scored
51.4/80Monthly downloads7,112 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagestrybuild-internals-api
dependents
ecosystemscrates
total_downloads132,661
monthly_downloads7,112
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?

47Weak · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
1.5/22.5Commit distributiontop contributor authored 93% of commits
13.5/13.5Contributor breadth30 contributors
10/10OpenSSF Scorecard: Contributorsproject has 10 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled30
top_contributor_share0.932
How it's scored
0/42Issue resolutionno issues or no data
0/30PR acceptanceno decided pull requests or no data
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/30 approved changesets -- score normalized to 0
Inputs used
merged_prs0
open_issues0
closed_issues0
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio
closed_unmerged_prs0
first_time_authors_30d0
first_time_prs_merged_30d0
first_time_prs_decided_30d0
Excluded from scoring (no data or not applicable): Issue resolution, PR acceptance, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domain
15.8/25Owner reach155 followers of hydro-project
25/25Track record70 public repos, account ~8 yr old
Inputs used
followers155
owner_typeOrganization
is_verifiedno
owner_loginhydro-project
public_repos70
account_age_days2,958
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 5 days ago
12/20Version history3 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagestrybuild-internals-api
ecosystemscrates
any_deprecatedno
min_days_since_publish5

Engineering Quality

Are baseline engineering and documentation practices in place?

42Weak · 19% of overall
How it's scored
24/24CI workflows1 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
0/20OpenSSF Scorecard: CI-Testsno data
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno
Excluded from scoring (no data or not applicable): OpenSSF Scorecard: CI-Tests. Remaining weights renormalized.

Documentation

15Critical
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/trybuild-internals-api
0/10Repository description
0/10Topics
0/10Wiki
Inputs used
topics
has_wikino
homepage
docs_sitehttps://docs.rs/trybuild-internals-api
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

56Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionbranch protection not enabled on development/release branches
0/2.5CI-Testsno data
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/30 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 10 contributing companies or organizations
10/10Dangerous-Workflowno dangerous workflow patterns detected
0/7.5Dependency-Update-Toolno update tool detected
5/5Fuzzingproject is fuzzed
2.5/2.5Licenselicense file detected
7.5/7.5Maintained26 commit(s) and 0 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/5SASTno SAST tool detected
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
7.5/7.5Token-PermissionsGitHub workflow tokens follow principle of least privilege
7.5/7.5Vulnerabilities0 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.6
Excluded from scoring (no data or not applicable): CI-Tests, Packaging, 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.

45Weak · 4% of overall
How it's scored
0/45Agent instructionsno CLAUDE.md / AGENTS.md / editor rules
0/15Machine-readable docs (llms.txt)
16.5/40Legible commit history31 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.31
agent_instruction_files
agent_instruction_max_bytes
How it's scored
12.6/18One-command bootstrapCargo.toml, fuzz/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checkingRust (statically typed)
0/10Reproducible environment
0/10Demonstrated agent practiceno agent-authored commits among the last 100
0/8Automated maintenanceno automated dependency updates observed
0/10OpenSSF Scorecard: Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 0
Inputs used
has_nixno
has_testsyes
lockfiles
has_dockerfileno
typed_languageyes
bootstrap_files
has_devcontainerno
has_linter_configno
typecheck_configs
agent_commit_share0
toolchain_manifestsCargo.toml, fuzz/Cargo.toml
dependency_bot_commit_share0
How it's scored
45/45Type-checkable codeRust (statically typed)
55/55Manageable file sizes0/63 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes26,311
source_files_sampled63
oversized_source_files0

Key facts

0GitHub stars
30contributors
54commits, last 12 months
5days since last push
0releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Community profile unavailable
  • No resolved dependencies carried a version and a supported ecosystem

More detail

OpenSSF Scorecard 5.6 / 10
5.6aggregate

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-30 06:53 UTC

10Binary-Artifactsno binaries found in the repo
0Branch-Protectionbranch protection not enabled on development/release branches
n/aCI-Testsno pull request found
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/30 approved changesets -- score normalized to 0
10Contributorsproject has 10 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained26 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
0SASTno SAST tool detected
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
10Token-PermissionsGitHub workflow tokens follow principle of least privilege
10Vulnerabilities0 existing vulnerabilities detected
Direct dependencies 8
RegistryPackageVersion constraintManifest
crates.iodissimilar1.0Cargo.toml
crates.ioglob0.3Cargo.toml
crates.ioserde1.0.194Cargo.toml
crates.ioserde_derive1.0.194Cargo.toml
crates.ioserde_json1.0.110Cargo.toml
crates.iotarget-triple1.0Cargo.toml
crates.iotermcolor1.0.4Cargo.toml
crates.iotoml1Cargo.toml
All dependencies 10

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

RegistryPackageVersionRelation
crates.iodissimilardirect
crates.ioglobdirect
crates.ioserdedirect
crates.ioserde_derivedirect
crates.ioserde_jsondirect
crates.iotarget-tripledirect
crates.iotermcolordirect
crates.iotomldirect
crates.ioautomodindirect
crates.iolibfuzzer-sysindirect
Dependency advisories not assessed

Advisory matching could not run for this report: No resolved dependencies carried a version and a supported ecosystem

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 statisticscrates.io.