`jsr:@std/yaml` vs `jsr:@eemeli/yaml` (aka `npm:yaml`)

I'm wondering whether anybody has looked more into this.

- `@std/yaml` says it's "ported from [js-yaml v3.13.1](https://github.com/nodeca/js-yaml/commit/665aadda42349dcae869f12040d9b10ef18d12da)"

- [e18e says](https://e18e.dev/docs/replacements/js-yaml.html) "js-yaml appears to be unmaintained and has known spec-compliance issues." They recommend `npm:yaml` instead, which is also availabe on JSR as [@eemeli/yaml](https://jsr.io/@eemeli/yaml)

So, should new projects better use `@eemeli/yaml`? Perhaps `@std/yaml` should be changed to be a thin wrapper around `jsr:@eemeli/yaml`? Or am I missing something, does the current code-base have other benefits?