Multiple memory safety issues

[Shnatsel]

An audit of this crate has uncovered multiple memory safety issues.

Please let me know how you'd like the issues to be reported - publicly on the issue tracker, privately via github or email, etc.

[lilith]

Thank you! You can send them to lilith@imazen.io. I wrote this initially as a way to ensure that I reached 100% feature parity when creating a full Rust port and hadn't looped back around to add my normal fuzzing infrastructure. I am kind of surprised it is already getting used!

[Shnatsel]

I'll submit the report shortly. Thanks!

The webp crate (libwebp bindings) is not in a great shape, with its own soundness issues like jaredforth/webp#51 and limitations like lacking ICC/Exif/XMP metadata. The lossy encoding in image-webp is in its infancy.
And I'm sure your full Rust port is great, but the license is too restrictive for my MIT/Apache project. So webpx looked promising.

[lilith]

v0.2.0 was published a few hours ago and should address those issues. Thank you so much for reporting them!

[Shnatsel]

Thanks for the swift fix!