PostSharp Blog

Security Notice: Data Leak Affecting a Limited Number of Accounts

by Gael Fraiteur on 07 Sep 2025

We regret to inform you of a data leak that occurred on the PostSharp Customer Portal between Wednesday, September 3rd, and Tuesday, September 9th.

READ

Breaking Update of PostSharp Caching adapter for Redis in 2025.1

by Gael Fraiteur on 01 Sep 2025

We have released a refactored version of PostSharp.Patterns.Caching.Backends.Redis in PostSharp 2025.1 to address a reliability issue that could surface in multi-node Redis deployments (master/replica or cluster) when cache dependencies are enabled under sustained load. The fix required a redesign of the internal data schema, which is why this is a breaking change (one-time cache purge). Outsid...

READ

PostSharp Is Now Source Available

by Gael Fraiteur on 07 Aug 2025

This spring we open-sourced Metalama. Continuing that push for transparency and dependability, PostSharp’s source code is now available to enterprise customers at no extra cost. You can access a read-only mirror of our primary Git repository, including every version back to 1.0 (2009). It’s an exact copy of the repo we use to build the product — down to the commas. We also provide a supported, ...

READ

Metalama Status Update, Mid Summer 2025

by Gael Fraiteur on 07 Aug 2025

It’s been over two months since our last status update. After a busy spring that peaked with the open-sourcing of Metalama, summer has been a bit quieter on the development side. Our focus shifted to releasing the source code of both PostSharp and Metalama’s premium packages under a source-available license, while fitting in some vacation time. But don’t worry, the open-source Metalama hasn’t b...

READ

Metalama Status Update, May 2025

by Gael Fraiteur on 30 May 2025

May is a time of growth and renewal, and Metalama is no exception. At the start of this month, we began a new chapter by open-sourcing our codebase, marking one of the most significant contributions to the .NET community this year. Throughout May, we focused on stabilizing our first open-source release, improving compliance with supply chain security and transparency best practices, and partici...

READ