Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unsafe-libyaml looks... unsafe? #193

Open
Gnurou opened this issue Nov 21, 2022 · 1 comment
Open

unsafe-libyaml looks... unsafe? #193

Gnurou opened this issue Nov 21, 2022 · 1 comment

Comments

@Gnurou
Copy link

Gnurou commented Nov 21, 2022

Hi and thanks for this very useful crate.

I am considering using this crate to use YAML instead of pure JSON for the configuration files of one of my projects, but am not sure what to think about the use of unsafe-libyaml... Safety is a big concern for us and this effectively introduces a bunch of unsafe code responsible for parsing arbitrary input.

Looking at the history I see that yaml-rust was used previously, but seems to have been abandoned in favor of unsafe-libyaml due to lack of maintenance. That's unfortunate but the decision is understandable.

Are there other alternatives that could be used to parse YAML? Or are my concerns about unsafe-libyaml unwarranted?

@davvid
Copy link

davvid commented Feb 3, 2024

In case you're still interested, my fork https://github.com/davvid/yaml-rust/ is actively maintained.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants