Why shouldn't gose be used for new implementations?

[Varpie]

The README states that "you should basically never use JWT, JWS, or JWE in a greenfield system", and that this package is meant to provide those capabilities to integrate with existing systems.

Why is it not recommended to use JOSE (and by extension, gose) for new implementations, and what are the recommended alternatives?
Is there any Gleam package that exists that implements the recommended alternative? If so, it could be interesting to mention it in the README as well.

[jtdowney]

It's hard to answer that without knowing your use case, so I can't really recommend an alternative. But the reason you want to avoid the JOSE standards is that they are overcomplicated for most use cases, and that overcomplication introduces complexity that an attacker can exploit. If you just want to encrypt some data with a key there is now amaro which I recently released because I knew folks would want something a bit higher level than kryptos but not as complex as gose.