Public record
Software health reportschema 0.26.0 · metrics 2.10.0 · 2026-07-22 02:15 UTC

greenticai / serde-yaml-gtc

Strongly typed YAML library for Rust maintained by Bourumir Wyngs

RustApache-2.0★ 1 star⑂ 0 forkssince Feb 2026forkView on GitHub ↗

greenticai/serde-yaml-gtc holds a health index of 63 out of 100, placing it in the Moderate band. It scores highest on Vitality (85/100) and lowest on Community & Adoption (26/100). It was last updated today. A single contributor accounts for most of its recent work.

63
overall / 100
Moderate

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.

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

Ownership

5 followers79 public repossince Feb 2026

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

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioserde_yaml_gtc2.6.298162010368,902100 days agoserdeserializationyamlencodingparser-implementations

Metrics by category

Vitality

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

85Excellent · 21% of overall
How it's scored
36/36Push recencylast push 0 days ago
19.4/36Commit cadence28/52 weeks with commits
18/18Commit volume212 commits in the last year
10/10OpenSSF Scorecard: Maintained22 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Inputs used
commits_last_year212
human_commit_share0.95
days_since_last_push0
active_weeks_last_year28
How it's scored
16.2/27Ships releases3 version tags (no GitHub releases)
36/36Release recencylatest release 21 days ago
27/27Release cadencea release every ~41.1 days
0/10OpenSSF Scorecard: Signed-Releasesno data
Inputs used
releases_count3
latest_release_tagv2.6.0
releases_from_tagsyes
days_since_latest_release21
mean_days_between_releases41.1
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?

26At Risk · 17% of overall
How it's scored
0/60Stars1 stars
0/25Forks0 forks
0/15Watchers0 watchers
Inputs used
forks0
stars1
watchers0
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonbelow_threshold
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_badges
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_services
has_pull_request_templateno
How it's scored
52.7/80Monthly downloads8,902 downloads/month across crates
0/20Registry dependentsnot reported by this ecosystem
Inputs used
packagesserde_yaml_gtc
dependents
ecosystemscrates
total_downloads40,867
monthly_downloads8,902
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?

64Moderate · 23% of overall
How it's scored
9/54Bus factor1 contributor(s) cover half of all commits
8.1/22.5Commit distributiontop contributor authored 64% of commits
13.5/13.5Contributor breadth41 contributors
10/10OpenSSF Scorecard: Contributorsproject has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled41
top_contributor_share0.638
How it's scored
0/42Issue resolutionno issues or no data
29.2/30PR acceptance37/38 decided PRs merged
0/13Newcomer PR acceptanceno first-time contributor's PR decided in 30d
0/15OpenSSF Scorecard: Code-ReviewFound 0/14 approved changesets -- score normalized to 0
Inputs used
merged_prs37
open_issues0
closed_issues0
prs_merged_7d
prs_decided_7d
prs_merged_30d
prs_decided_30d
issue_closed_ratio
closed_unmerged_prs1
first_time_authors_30d
first_time_prs_merged_30d
first_time_prs_decided_30d
Excluded from scoring (no data or not applicable): Issue resolution, Newcomer PR acceptance. Remaining weights renormalized.
How it's scored
30/30Ownership backingorganization-owned
0/20Verified domainverified-domain status not read for this organization
5.6/25Owner reach5 followers of greenticai
13.8/25Track record79 public repos, account ~0 yr old
Inputs used
followers5
owner_typeOrganization
is_verified
owner_logingreenticai
public_repos79
account_age_days155
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable1 package(s) on crates
35/35Publish recencylatest publish 0 days ago
20/20Version history10 published versions
20/20Not deprecatedactive, not deprecated or yanked
Inputs used
packagesserde_yaml_gtc
ecosystemscrates
any_deprecatedno
min_days_since_publish0

Engineering Quality

Are baseline engineering and documentation practices in place?

47Weak · 19% of overall
How it's scored
24/24CI workflows11 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/6.4.editorconfig
14/20OpenSSF Scorecard: CI-Tests14 out of 18 merged PRs checked by a CI test -- score normalized to 7
Inputs used
has_ciyes
has_testsyes
has_editorconfigno
has_linter_configno
has_precommit_configno

Documentation

25At Risk
How it's scored
0/30README
0/25Documentation directory
15/15Documentation / homepage sitehttps://docs.rs/serde_yaml_gtc
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics
has_wikiyes
homepage
docs_sitehttps://docs.rs/serde_yaml_gtc
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

61Moderate · 16% of overall
How it's scored
7.5/7.5Binary-Artifactsno binaries found in the repo
0/7.5Branch-Protectionno data
1.8/2.5CI-Tests14 out of 18 merged PRs checked by a CI test -- score normalized to 7
0/2.5CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0/7.5Code-ReviewFound 0/14 approved changesets -- score normalized to 0
2.5/2.5Contributorsproject has 17 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.5Maintained22 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/5SASTSAST tool is not run on all commits -- score normalized to 0
0/5Security-Policysecurity policy file not detected
0/7.5Signed-Releasesno data
0/7.5Token-Permissionsdetected GitHub workflow tokens with excessive permissions
6.8/7.5Vulnerabilities1 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated15
scorecard_versionv5.5.0
checks_inconclusive3
scorecard_aggregate5.1
Excluded from scoring (no data or not applicable): Branch-Protection, Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

100Exceptional
How it's scored
35/35Direct dependencies free of known advisoriesno direct dependency carries a known advisory
0/25Indirect dependencies free of known advisoriestransitive set not separable from development and test dependencies in this scope
0/40No advisories left outstandingno advisory carries a publication date
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages85
unassessed_packages0
affected_by_severityunknown 1
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 85 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.

72Good · 4% of overall
How it's scored
45/45Agent instructionsAGENTS.md
0/15Machine-readable docs (llms.txt)
34.8/40Legible commit history62 of 95 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url
legible_history_share0.653
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,468
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)
10/10Reproducible environmentlockfile
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
lockfilesCargo.lock
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)
54.8/55Manageable file sizes1/341 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes80,211
source_files_sampled341
oversized_source_files1

Key facts

1GitHub stars
41contributors
212commits, last 12 months
0days since last push
3releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

  • Community profile unavailable
  • deps.dev does not index crates:serde_yaml_gtc@2.6.29816201036; advisories assessed against the repository dependency graph instead

More detail

OpenSSF Scorecard 5.1 / 10
5.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).Scorecard v5.5.0 · 2026-07-22 02:15 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
7CI-Tests14 out of 18 merged PRs checked by a CI test -- score normalized to 7
0CII-Best-Practicesno effort to earn an OpenSSF best practices badge detected
0Code-ReviewFound 0/14 approved changesets -- score normalized to 0
10Contributorsproject has 17 contributing companies or organizations
10Dangerous-Workflowno dangerous workflow patterns detected
0Dependency-Update-Toolno update tool detected
10Fuzzingproject is fuzzed
10Licenselicense file detected
10Maintained22 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
0Security-Policysecurity policy file not detected
n/aSigned-Releasesno releases found
0Token-Permissionsdetected GitHub workflow tokens with excessive permissions
9Vulnerabilities1 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
crates.ioindexmap>=2.0, <3Cargo.toml
crates.ioitoa1.0Cargo.toml
crates.iozmij1.0Cargo.toml
crates.iounsafe-libyaml-norway0.2Cargo.toml
crates.iobase64>=0.21, <0.23Cargo.toml
crates.iosaphyr-parser0.0.6Cargo.toml
crates.ioregex>= 1.8, < 1.13Cargo.toml
crates.ionum-traits>= 0.2.0, < 0.2.20Cargo.toml
crates.ioserde1.0Cargo.toml
All dependencies 85

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

RegistryPackageVersionRelation
crates.iobase640.22.1direct
crates.ioindexmap2.13.0direct
crates.ioindexmap2.14.0direct
crates.ioitoa1.0.15direct
crates.ioitoa1.0.18direct
crates.ionum-traits0.2.19direct
crates.ioregex1.12.2direct
crates.ioregex1.12.3direct
crates.iosaphyr-parser0.0.6direct
crates.ioserde1.0.219direct
crates.ioserde1.0.228direct
crates.iounsafe-libyaml-norway0.2.15direct
crates.iozmij1.0.12direct
crates.iozmij1.0.21direct
crates.ioaho-corasick1.1.4indirect
crates.ioandroid_system_properties0.1.5indirect
crates.ioanyhow1.0.102indirect
crates.ioarbitrary1.4.1indirect
crates.ioarraydeque0.5.1indirect
crates.ioautocfg1.5.0indirect
crates.iobitflags2.9.1indirect
crates.iobumpalo3.20.2indirect
crates.iocc1.2.30indirect
crates.iocc1.2.60indirect
crates.iocfg-if1.0.1indirect
crates.iocfg-if1.0.4indirect
crates.iochrono0.4.44indirect
crates.iocore-foundation-sys0.8.7indirect
crates.ioequivalent1.0.2indirect
crates.iofind-msvc-tools0.1.9indirect
crates.iofoldhash0.1.5indirect
crates.iogetrandom0.3.3indirect
crates.iohashbrown0.15.4indirect
crates.iohashbrown0.15.5indirect
crates.iohashbrown0.16.1indirect
crates.iohashbrown0.17.0indirect
crates.iohashlink0.10.0indirect
crates.ioiana-time-zone0.1.65indirect
crates.ioiana-time-zone-haiku0.1.2indirect
crates.ioindoc2.0.7indirect
crates.iojobserver0.1.33indirect
crates.iojs-sys0.3.95indirect
crates.iolibc0.2.174indirect
crates.iolibc0.2.185indirect
crates.iolibfuzzer-sys0.4.10indirect
crates.iolog0.4.29indirect
crates.iomemchr2.7.6indirect
crates.iomemchr2.8.0indirect
crates.ioonce_cell1.21.4indirect
crates.ioproc-macro21.0.106indirect
crates.ioproc-macro21.0.95indirect
crates.ioquote1.0.40indirect
crates.ioquote1.0.45indirect
crates.ior-efi5.3.0indirect
crates.ioregex-automata0.4.13indirect
crates.ioregex-automata0.4.14indirect
crates.ioregex-syntax0.8.10indirect
crates.ioregex-syntax0.8.8indirect
crates.iorustversion1.0.22indirect
crates.ioryu1.0.23indirect
crates.ioserde_bytes0.11.19indirect
crates.ioserde_core1.0.228indirect
crates.ioserde_derive1.0.219indirect
crates.ioserde_derive1.0.228indirect
crates.ioserde_json1.0.149indirect
crates.ioserde_repr0.1.20indirect
crates.ioserde_yaml0.9.34+deprecatedindirect
crates.ioshlex1.3.0indirect
crates.iosyn2.0.104indirect
crates.iosyn2.0.117indirect
crates.iounicode-ident1.0.18indirect
crates.iounicode-ident1.0.24indirect
crates.iounsafe-libyaml0.2.11indirect
crates.iowasi0.14.2+wasi-0.2.4indirect
crates.iowasm-bindgen0.2.118indirect
crates.iowasm-bindgen-macro0.2.118indirect
crates.iowasm-bindgen-macro-support0.2.118indirect
crates.iowasm-bindgen-shared0.2.118indirect
crates.iowindows-core0.62.2indirect
crates.iowindows-implement0.60.2indirect
crates.iowindows-interface0.59.3indirect
crates.iowindows-link0.2.1indirect
crates.iowindows-result0.4.1indirect
crates.iowindows-strings0.5.1indirect
crates.iowit-bindgen-rt0.39.0indirect
Dependency advisories 1

This repository publishes no package the index resolves, so its own dependency graph was assessed — 85 packages, which also include development and test pins that never ship: 1 carry known advisories, of which 0 are direct.

PackageVersionRelationSeverityAdvisoriesFixed in
anyhow1.0.102indirectunknown11.0.103

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.26.0 — full methodology · metrics wiki.

How one result sits in the wider record: aggregate statisticscrates.io.