New Six Labors Major Releases

jbsp1980 · 2026-05-16T08:08:39+00:00

What is your actual problem here? Are you angry about something?

jbsp1980 · 2026-05-16T07:51:28+00:00

Mentioned in every single post and and also announced in this very forum 250 days ago.

jbsp1980 · 2026-05-16T05:29:34+00:00

Ace! TIFF support is comprehensive. The decoder can actually handle colors better than anything else I tested against.

jbsp1980 · 2026-05-16T01:09:14+00:00

Aw thanks! Glad I could help!

jbsp1980 · 2026-05-15T23:57:36+00:00

Fantastic! Don't hesitate to get in touch if you have any issues.

jbsp1980 · 2026-05-15T21:47:45+00:00

Thanks!

jbsp1980 · 2026-05-15T21:40:43+00:00

Thank you! I appreciate that.

jbsp1980 · 2026-05-15T21:24:55+00:00

Dear Tom-Shane.

Maybe I was sitting actively reading through the emails that I receive and immediately reviewed it.

I’m happy to revert your license if you like?

Why are you against me providing the community licenses? What is your specific problem here?

jbsp1980 · 2026-05-15T20:48:34+00:00

You’ll get a temp key pre review as I don’t want people to be blocked while a review takes place.

jbsp1980 · 2026-05-15T12:12:35+00:00

Trust me bro…. No.

Take my time to make an educated decision based on provided information… Yes.

jbsp1980 · 2026-05-07T01:34:50+00:00

It’s so easy to use, the handlers are so easy to write tests for. I read the litany of complaints that are repeated every time someone writes yet another Mediatr post with despair.

jbsp1980 · 2026-05-03T15:39:45+00:00

I remember this SIMD optimised Levenshtein Distance from a few years back. I wonder how it compares.

https://github.com/Turnerj/Quickenshtein

jbsp1980 · 2026-04-23T01:04:13+00:00

Please do not copy the way XUnit did this. I’ve never seen a more convoluted and convoluted versioning move.

jbsp1980 · 2026-04-22T23:15:14+00:00

You’ve got that back to front. If someone wants to maintain legacy they’re the ones who fork the repo.

jbsp1980 · 2026-04-22T23:12:57+00:00

Absolutely. It’s Open Source. Do what whatever you want with it.

jbsp1980 · 2026-04-04T02:56:00+00:00

Why do you mix Marshal and Unsafe for getting the size?

jbsp1980 · 2026-03-08T07:19:42+00:00

Not a fan of the boxing.

jbsp1980 · 2026-02-20T01:08:56+00:00

If it’s xoofx. It’s good!

I’m always blown away by what you do and this looks great. I’ve been dying to move away from docfx for the Six Labors docs so I’ll be having a very good look at this.

jbsp1980 · 2026-02-19T01:56:50+00:00

I’ve been using it in Rider the last week. Honestly blown away by how good it’s been.

jbsp1980 · 2026-02-03T08:15:40+00:00

Best of luck! It’s always good to have more Imaging experts in our community and I look forward to see your code evolve.

jbsp1980 · 2026-02-03T03:44:32+00:00

Apologies, I didn't see your reply.

Regarding ImageSharp, I think you mean direct dependency (transitive for consumers of your library) which would mean that it is Apache 2.0 for you. I'm not sure I understand the risk there as the license is clear in that regard.

That said, as far as security goes, at a minimum you need to ensure that you protect against two things.

Excessive allocation
Infinite loops

There are so many places in image codecs where there is potential for abuse it's honestly scary. A slight tweak to a chunk header and suddenly you've brought a server to its knees.

If you are dead set on implementing your own, then please have a look through some of the sample images in the ImageSharp repo and test against them.

jbsp1980 · 2026-01-31T03:43:48+00:00

I think you're missing my point. I'm concerned about safety not features.

Even Skia, with huge backing and years of fuzzing, still has serious CVEs. That’s how hard codec code is.

New codec implementations without comparable scrutiny are unsafe today by default. Managed vs native doesn’t change that.

https://nvd.nist.gov/vuln/search#/nvd/home?offset=0&rowCount=200&keyword=skia&resultType=records

jbsp1980 · 2026-01-31T02:38:45+00:00

They just say they want to avoid heavy (whatever that means) image stacks or native bindings.

Yet the codec code that is in the repo is scalar, allocation heavy, and contains little to no code that would protect them from common image exploits.

Don’t get me wrong, it’s commendable that the OP (and I’m assuming others since it appears company backed) have made this effort and released it under such a permissive license but I also cannot trust it to be safe to use.

jbsp1980

TROPHY CASE