Update the SixLabors package #489

Activity

1. zur003 commented on Jan 5, 2026

   

   zur003

   on Jan 5, 2026

   More actions

   I suggest you consider using PDFSharp rather than PdfSharpCore.

   👍React with 👍2Reacted by kyriacosmichael and Thomas Hövel
2. tossnet commented on Jan 15, 2026

   

   tossnet

   on Jan 15, 2026

   Last edited by tossnet

   More actions

   I suggest you consider using PDFSharp rather than PdfSharpCore.

   @zur003 Is it also free to use?
3. zur003 commented on Jan 15, 2026

   

   zur003

   on Jan 15, 2026

   More actions

   I suggest you consider using PDFSharp rather than PdfSharpCore.

   @zur003 Is it also free to use?

   Yes, it's open source under the MIT license.

   ❤️React with ❤️1Reacted by Christophe Peugnet
4. jochenwezel commented on Mar 17, 2026

   

   jochenwezel

   on Mar 17, 2026

   More actions

   I like to stay at PdfSharpCore since it doesn't depend on windows platform. So back to the origin request: it would be great to see the SixLabors package reference being refreshed to a newer version without security warning :-)

   👀React with 👀1Reacted by Thomas Hövel
5. jochenwezel commented on Mar 17, 2026

   

   jochenwezel

   on Mar 17, 2026

   More actions

   I already see there is a pull request #476 which might fix this issue. Please can somebody review/merge it?

   👍React with 👍2Reacted by kyriacosmichael and Justin Toth
6. TH-Soft commented on Apr 21, 2026

   

   TH-Soft

   on Apr 21, 2026

   More actions

   I like to stay at PdfSharpCore since it doesn't depend on windows platform.

   Since April 3, 2023, PDFsharp no longer depends on Windows.
   https://www.nuget.org/packages/PDFsharp/7.0.0-preview-1#supportedframeworks-body-tab

   👀React with 👀1Reacted by Davide G.
7. TH-Soft commented on Apr 21, 2026

   

   TH-Soft

   on Apr 21, 2026

   More actions

   Can we update the SixLabors package as there is a security vulnerability.

   And maybe add .NET 10 as target framework. And remove .NET 5, .NET6, and .NET 7 as target frameworks as they are out of support.

   👍React with 👍1Reacted by Daniel Salas
8. tossnet commented on Oct 14, 2026

   

   tossnet

   on Oct 14, 2026

   More actions

   3. > > I suggest you consider using PDFSharp rather than PdfSharpCore.
   >
   >
   > @zur003 Is it also free to use?

   Yes, it's open source under the MIT license.
   

   ❌ Update for anyone landing here: since PDFsharp 6.5.0, the license is no longer MIT. You must now choose between AGPL (PdfSharpLicense.SetAgplLicense()) or a paid commercial license (PdfSharpLicense.LoadLicense(...)). Worth checking before migrating, especially for closed-source or SaaS projects. Details: https://docs.pdfsharp.net/General/History.html#ps-6-5-0