Public record
Software health reportschema 0.34.0 · metrics 2.10.0 · 2026-10-19 18:45 UTC

bourumir-wyngs / serde-yaml-bw

Strongly typed YAML library for Rust maintained by Bourumir Wyngs

RustApache-2.0★ 37 stars⑂ 5 forkssince May 2024forkView on GitHub ↗
KindLibraryhow this is determined

bourumir-wyngs/serde-yaml-bw holds a health index of 56 out of 100, placing it in the Moderate band. It scores highest on Vitality (69/100) and lowest on Engineering Quality (39/100). It was last updated 42 days ago. A single contributor accounts for most of its recent work.

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

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

Ownership

BourumirPersonal account
21 followers26 public repossince Mar 2023ETH Zurich

This repository is owned by a personal account. A single-owner project carries more continuity risk than an organization-backed one.

Package ecosystems

RegistryPackageVersionDownloads / moVersionsLast publishTags
crates.ioserde_yaml_bw2.5.855,3742442 days agoserializationyamlserdeencodingparser-implementations

Metrics by category

Vitality

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

69Good · 21% of overall

Development activity

49Weak
How it's scored
18/36Push recency — last push 42 days ago
9/36Commit cadence — 13/52 weeks with commits
16.6/18Commit volume — 70 commits in the last year
5/10OpenSSF Scorecard: Maintained — 5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
Inputs used
commits_last_year70
human_commit_share1
days_since_last_push42
active_weeks_last_year13

Release discipline

100Exceptional
How it's scored
27/27Ships releases — 18 releases published
36/36Release recency — latest release 42 days ago
27/27Release cadence — a release every ~42.3 days
0/10OpenSSF Scorecard: Signed-Releases — no data
Inputs used
releases_count18
latest_release_tag2.5.8
releases_from_tagsno
days_since_latest_release42
mean_days_between_releases42.3
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

Popularity & adoption

30At Risk
How it's scored
25.2/60Stars — 37 stars
5/25Forks — 5 forks
0/15Watchers — 2 watchers
Inputs used
forks5
stars37
watchers2
growth_stateunverified
growth_factor_pct100
growth_unverified_reasonno_history

Community health

25At Risk
How it's scored
0/22.5README
22.5/22.5License — recognized 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_badges8
has_contributingno
has_issue_templateno
has_code_of_conductno
readme_badge_servicesgithub.com, shields.io
has_pull_request_templateno

Ecosystem adoption (downloads)

79Good
How it's scored
63.2/80Monthly downloads — 55,374 downloads/month across crates
0/20Registry dependents — not reported by this ecosystem
Inputs used
packagesserde_yaml_bw
dependents—
ecosystemscrates
total_downloads355,585
monthly_downloads55,374
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?

63Moderate · 23% of overall

Maintainer resilience (bus factor)

40Weak
How it's scored
9/54Bus factor — 1 contributor(s) cover half of all commits
7.7/22.5Commit distribution — top contributor authored 66% of commits
13.5/13.5Contributor breadth — 40 contributors
10/10OpenSSF Scorecard: Contributors — project has 17 contributing companies or organizations
Inputs used
bus_factor1
contributors_sampled40
top_contributor_share0.656

Issue & PR responsiveness

76Good
How it's scored
42/42Issue resolution — 100% of issues closed
23.9/30PR acceptance — 156/196 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_prs156
open_issues0
closed_issues5
prs_merged_7d0
prs_decided_7d0
prs_merged_30d0
prs_decided_30d0
issue_closed_ratio1
closed_unmerged_prs40
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.

Ownership & stewardship

47Weak
How it's scored
10/30Ownership backing — personal (user) account
0/20Verified domain — not applicable to user accounts
9.7/25Owner reach — 21 followers of bourumir-wyngs
17.7/25Track record — 26 public repos, account ~3 yr old
Inputs used
followers21
owner_typeUser
is_verified—
owner_loginbourumir-wyngs
public_repos26
account_age_days1,323
Excluded from scoring (no data or not applicable): Verified domain. Remaining weights renormalized.

Package maintenance

100Exceptional
How it's scored
25/25Published & resolvable — 1 package(s) on crates
35/35Publish recency — latest publish 42 days ago
20/20Version history — 24 published versions
20/20Not deprecated — active, not deprecated or yanked
Inputs used
packagesserde_yaml_bw
ecosystemscrates
any_deprecatedno
min_days_since_publish42

Engineering Quality

Are baseline engineering and documentation practices in place?

39Weak · 19% of overall

Engineering practices

48Weak
How it's scored
24/24CI workflows — 4 workflow(s)
24/24Tests present
0/16Linter config
0/9.6Pre-commit hooks
0/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_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 site — https://docs.rs/serde_yaml_bw/latest/serde_yaml_bw/
0/10Repository description
0/10Topics
10/10Wiki
Inputs used
topics—
has_wikiyes
homepage—
docs_sitehttps://docs.rs/serde_yaml_bw/latest/serde_yaml_bw/
has_readmeno
has_docs_dirno
has_descriptionno

Security

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

52Moderate · 16% of overall

Security posture

42Weak
How it's scored
7.5/7.5Binary-Artifacts — no binaries found in the repo
0.8/7.5Branch-Protection — branch protection is not maximal on development and all release branches
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
2.5/2.5Contributors — project has 17 contributing companies or organizations
10/10Dangerous-Workflow — no dangerous workflow patterns detected
0/7.5Dependency-Update-Tool — no update tool detected
5/5Fuzzing — project is fuzzed
2.5/2.5License — license file detected
3.8/7.5Maintained — 5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
0/5Packaging — no data
1/5Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
0/5SAST — SAST tool is not run on all commits -- score normalized to 0
0/5Security-Policy — security policy file not detected
0/7.5Signed-Releases — no data
0/7.5Token-Permissions — detected GitHub workflow tokens with excessive permissions
6/7.5Vulnerabilities — 2 existing vulnerabilities detected
Inputs used
sourceopenssf_scorecard
checks_evaluated16
scorecard_versionv5.5.0
checks_inconclusive2
scorecard_aggregate4.2
Excluded from scoring (no data or not applicable): Packaging, Signed-Releases. Remaining weights renormalized.

Dependency advisories

91Excellent
How it's scored
35/35Direct dependencies free of known advisories — no direct dependency carries a known advisory
19/25Indirect dependencies free of known advisories — 1 affected: unsafe-libyaml 0.2.11 (unknown)
37.2/40No advisories left outstanding — 1 advisory-carrying package(s) unaddressed past 90 days; oldest published 938 days ago
Inputs used
sourceosv
advisories1
affected_packages1
assessed_packages61
unassessed_packages0
affected_by_severityunknown 1
direct_affected_packages0
Matched the crates:serde_yaml_bw@2.5.8 runtime dependency closure — what installing the published package pulls in — 61 packages. 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.

62Moderate · 4% of overall

Agent context & guidance

48Weak
How it's scored
45/45Agent instructions — AGENTS.md
0/15Machine-readable docs (llms.txt)
2.7/40Legible commit history — 5 of 100 human commits state their intent (structured subject or explanatory body)
Inputs used
has_llms_txtno
llms_txt_url—
legible_history_share0.05
agent_instruction_filesAGENTS.md
agent_instruction_max_bytes1,468

Verify loop (build / test / typecheck)

58Moderate
How it's scored
12.6/18One-command bootstrap — Cargo.toml, fuzz/Cargo.toml (toolchain convention, no task runner)
22/22Automated tests
0/11Lint / format config
11/11Static type checking — Rust (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
2/10OpenSSF Scorecard: Pinned-Dependencies — dependency not pinned by hash detected -- score normalized to 2
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

Code legibility for models

100Exceptional
How it's scored
45/45Type-checkable code — Rust (statically typed)
54.8/55Manageable file sizes — 1/344 source files over 60KB
Inputs used
primary_languageRust
largest_source_bytes86,568
source_files_sampled344
oversized_source_files1

Key facts

37GitHub stars
40contributors
70commits, last 12 months
42days since last push
18releases
1bus factor
0open issues
crates.iopackage ecosystems

Data collection warnings

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

More detail

Star and fork history 0 ★ / 5 ⇿
0Stars
5Forks
13Releases

When each star and fork was added, collected from GitHub and bucketed by day. Cumulative growth sits directly above the daily additions it is made of, so the two read against each other: steady organic accretion looks nothing like an abrupt, short-lived burst. Where that difference is measurable, it is reported as growth authenticity.

12345512025-072026-022026-09
Major 0Minor 3Patch 9

Each point covers 2 days.

OpenSSF Scorecard 4.2 / 10
4.2aggregate

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-10-19 18:45 UTC

10Binary-Artifactsno binaries found in the repo
1Branch-Protectionbranch protection is not maximal on development and all release branches
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
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
5Maintained5 commit(s) and 1 issue activity found in the last 90 days -- score normalized to 5
n/aPackagingpackaging workflow not detected
2Pinned-Dependenciesdependency not pinned by hash detected -- score normalized to 2
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
8Vulnerabilities2 existing vulnerabilities detected
Direct dependencies 9
RegistryPackageVersion constraintManifest
crates.ioindexmap2.0Cargo.toml
crates.ioitoa1.0Cargo.toml
crates.iozmij1.0Cargo.toml
crates.ioserde1.0Cargo.toml
crates.iounsafe-libyaml-norway0.2Cargo.toml
crates.iobase64>=0.21, <0.24Cargo.toml
crates.iosaphyr-parser1Cargo.toml
crates.ioregex1.8Cargo.toml
crates.ionum-traits0.2.0Cargo.toml
All dependencies 75

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

RegistryPackageVersionRelation
crates.iobase640.22.1direct
crates.iobase640.23.1direct
crates.ioindexmap2.13.0direct
crates.ioitoa1.0.11direct
crates.ioitoa1.0.15direct
crates.ionum-traits0.2.19direct
crates.ioregex1.12.2direct
crates.ioserde1.0.218direct
crates.ioserde1.0.219direct
crates.iounsafe-libyaml-norway0.2.15direct
crates.iozmij1.0.12direct
crates.ioaho-corasick1.1.4indirect
crates.ioandroid-tzdata0.1.1indirect
crates.ioandroid_system_properties0.1.5indirect
crates.ioanyhow1.0.98indirect
crates.ioarbitrary1.4.1indirect
crates.ioarraydeque0.5.1indirect
crates.ioautocfg1.5.0indirect
crates.iobitflags2.9.1indirect
crates.iobumpalo3.19.0indirect
crates.iocc1.2.30indirect
crates.iocfg-if1.0.1indirect
crates.iochrono0.4.41indirect
crates.iocore-foundation-sys0.8.7indirect
crates.ioequivalent1.0.1indirect
crates.ioequivalent1.0.2indirect
crates.iogetrandom0.3.3indirect
crates.iogranit-parser1.1.0indirect
crates.iohashbrown0.16.1indirect
crates.ioiana-time-zone0.1.63indirect
crates.ioiana-time-zone-haiku0.1.2indirect
crates.ioindoc2.0.5indirect
crates.iojobserver0.1.33indirect
crates.iojs-sys0.3.77indirect
crates.iolibc0.2.174indirect
crates.iolibfuzzer-sys0.4.10indirect
crates.iolog0.4.27indirect
crates.iomemchr2.7.4indirect
crates.iomemchr2.7.6indirect
crates.ioonce_cell1.21.3indirect
crates.ioproc-macro21.0.93indirect
crates.ioproc-macro21.0.95indirect
crates.ioquote1.0.36indirect
crates.ioquote1.0.40indirect
crates.ior-efi5.3.0indirect
crates.ioregex-automata0.4.13indirect
crates.ioregex-syntax0.8.8indirect
crates.iorustversion1.0.21indirect
crates.ioryu1.0.17indirect
crates.ioserde_bytes0.11.17indirect
crates.ioserde_derive1.0.218indirect
crates.ioserde_derive1.0.219indirect
crates.ioserde_json1.0.140indirect
crates.ioserde_repr0.1.20indirect
crates.ioserde_yaml0.9.34+deprecatedindirect
crates.ioshlex1.3.0indirect
crates.iosmallvec1.15.1indirect
crates.iosyn2.0.104indirect
crates.iosyn2.0.98indirect
crates.iounicode-ident1.0.12indirect
crates.iounicode-ident1.0.18indirect
crates.iounsafe-libyaml0.2.11indirect
crates.iowasi0.14.2+wasi-0.2.4indirect
crates.iowasm-bindgen0.2.100indirect
crates.iowasm-bindgen-backend0.2.100indirect
crates.iowasm-bindgen-macro0.2.100indirect
crates.iowasm-bindgen-macro-support0.2.100indirect
crates.iowasm-bindgen-shared0.2.100indirect
crates.iowindows-core0.61.2indirect
crates.iowindows-implement0.60.0indirect
crates.iowindows-interface0.59.1indirect
crates.iowindows-link0.1.3indirect
crates.iowindows-result0.3.4indirect
crates.iowindows-strings0.4.2indirect
crates.iowit-bindgen-rt0.39.0indirect
Dependency advisories 1

Installing crates:serde_yaml_bw@2.5.8 pulls in 61 packages, direct and transitive: 1 carry known advisories, of which 0 are direct dependencies.

PackageVersionRelationSeverityAdvisoriesFixed in
unsafe-libyaml0.2.11indirectunknown1—

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.

Related records

Inspected repositories sharing catalogue tags or ecosystems with bourumir-wyngs/serde-yaml-bw. Read them side by side →

91sebastienrousseau/noyalibA YAML 1.2 parser and serialiser for Rust: zero unsafe, full serde integration, lossless CST editing, JSON Schema validation, 406/406 on the official test suite. Core of a six-crate ecosystem with a CLI, LSP, MCP server, WASM bindings, and a serde_yaml drop-in.Excellent91bourumir-wyngs/serde-saphyrA strongly typed, comment-supporting YAML deserializer that deserializes YAML directly into your Rust types without constructing an intermediate tree of “abstract values.” Excellent87cloudwego/sonic-rsA fast Rust JSON library based on SIMD.Excellent84serde-rs/jsonStrongly typed JSON library for RustExcellent94alloy-rs/coreHigh-performance, well-tested & documented core libraries for Ethereum, in RustExceptional94toml-rs/tomlRust TOML ParserExceptional

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 — crates.io.