Takeover maintainance of `microaeson`?

It seems like `stan` is the only (direct) user of [`microaeson`](https://hackage.haskell.org/package/microaeson).
https://github.com/kowainik/stan/blob/78e4ae11a2eba1e338900c00951213087506de7a/stan.cabal#L165

I am not using microaeson so I should/want not maintain it.

@tomjaguarpaw Would you be willing to take over `microaeson`?

It has been very little effort to maintain it so far.

The issue concerns taking over maintenance of the external microaeson package, which is identified as a direct dependency of stan in stan.cabal. No implementation files or tests are named; first confirm whether the proposed maintainer wants ownership, and consider the issue complete only when the maintenance responsibility is explicitly decided.

Written by the indexing model from the issue text.