Accidentally archived or deliberately archived then unarchived?

[sean-]

Quick question: this project was archived and then unarchived. Was this deliberate and we should take this as a sign that ladon should not be used, or was it an accident and ladon is "safe" for use? Thanks in advance.

[aeneasr]

Yeah that was a mistake on my part! ORY Ladon is considered stable, but we deprecated the SQL store as it had many issues. The library is safe to use and there have not been any bugs or missing features in the past 6 months which I take as "being stable". That said, we no longer use ORY Ladon internally for ORY Keto, so we're not deeply invested in progressing the functionality of this project, but we're definitely monitoring it and answering issues and fix bugs if some come up!

So yes, it was a mistake in communication by me and I am sorry for that. And yes, it's still encouraged to use this library, but we are not actively moving it forward as it is considered stable.

[sean-]

Thanks @aeneasr . I was confused when I saw ladon still vendored in keto, which was my primary source of curio. If keto isn't using ladon, then what's keto using for it's policy evaluation language?

[aeneasr]

I've switched to rego which is implemented by opa. Keto will provide best-practice patterns which are implemented on top of OPA and provide a clear and concise API. It's also a bit faster than Ladon, specifically the Ladon SQL manager which I deprecated because it had so issues regarding scalability and also some bugs because of missing locks.

[sean-]

Got it, thank you for the detail. Seeing keto still have ladon vendored and in use was confusing. Is this opa work in a branch someplace or is it now mainline?

[aeneasr]

There's a PR open, that's the one.