serde_yaml is unmaintained
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 1.2k
- Forks
- 544
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 45
Description
https://crates.io/crates/serde_yaml latest version is "v0.9.34+deprecated" - uploaded March 2024
Repo https://github.com/dtolnay/serde-yaml was also archived.
Forks:
https://github.com/sebastienrousseau/serde_yml/commits/master/ - 110 commits - uses https://crates.io/crates/libyml instead of also unmaintained(see https://github.com/rustsec/advisory-db/issues/2212)unsafe-libyaml- https://crates.io/crates/serde_yaml_ng - ~30 commits / quite active at https://github.com/acatton/serde-yaml-ng/commits/master/
- https://crates.io/crates/serde_norway - ~30 commits / quite active at https://github.com/cafkafk/serde-norway , however states that they are not committed to maintaining long term
- https://crates.io/crates/serde_yaml_ok - one enhancement at https://github.com/mkovaxx/serde-yaml-ok/commits/main/
- https://github.com/chhe/serde-yaml - branches off 0.8 instead of 0.9 - @chhe , what was the reason for doing this?
Alternatives:
- https://crates.io/crates/serde_yaml2 , project started in April 2024 - https://github.com/zim32/serde_yaml2/commits/main/ ; uses https://github.com/Ethiraric/yaml-rust2 instead of libyaml - Incompatibilities being collated at https://github.com/zim32/serde_yaml2/issues/2
- https://github.com/KmolYuan/yaml-peg-rs - no yaml dependency used
- https://github.com/qiuchengxuan/serde-yaml-core - not on crates.io - "serde-yaml for no_std programs"
- https://github.com/s1s5/serde-yaml - another attempt at using yaml-rust2 - not published to crates.io
https://github.com/g-plane/pretty_yaml - no yaml dependency usedno serde support
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is identified in the issue. Start by reviewing the listed serde_yaml forks and alternatives, including their compatibility and maintenance status; done means reaching a supported resolution for the unmaintained dependency in the advisory database.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100