I think it's just one of those things that is "done" -- is the staleness just its deps?

(Leiningen still uses it: https://codeberg.org/leiningen/leiningen/src/branch/main/leiningen-core/project.clj#L12 and I think I've seen it referenced in a few other projects, but it is definitely used less than it used to be)

Stale deps with CVEs on it.

Ah, worth bumping and cutting a new release then. Maybe then let the lein folks know via an issue since they're working on 2.10.1 of Leiningen right now.

2.10.1?

Away from computer but I thought we were around 2.90 or something?

Latest commit on Leiningen: https://codeberg.org/leiningen/leiningen/commit/acb7833eb4dc57ada7b789fe18b3273951fc5b0f "Bump version to 2.10.1-SNAPSHOT"

Probs using 2.9 something then :)

There's also no release automation and other maintenancy type things.

@U04V70XH6 I was looking at my options at properly determining deps for libs for cljdoc, hence peek at pomegranate. I'm guessing it is a potentially viable choice today. (tools.deps almost did the trick but it filters out provided deps which cljdoc is interested in seeing).