Also, whilst mucking about in here: some care to alignment would be helpful: pretty much anything in an ordinal domain would benefit from being right-aligned. size, specifically, would also benefit from always including one trailing decimal place, as per prefix-dev/rattler-build#1399

name           version        build                 size    kind   source
openssl        3.6.0          h26f9b46_0        3 MiB       conda  https://conda.anaconda.org/conda-forge/
oras-py        0.1.14         pyhd8ed1ab_0      33.6 KiB    conda  https://conda.anaconda.org/conda-forge/
packaging      25.0           pyh29332c3_1      61 KiB      conda  https://conda.anaconda.org/conda-forge/

vs:

name           version        build                 size    kind   source
openssl        3.6.0          h26f9b46_0         3.0 MiB    conda  https://conda.anaconda.org/conda-forge/
oras-py        0.1.14         pyhd8ed1ab_0      33.6 KiB    conda  https://conda.anaconda.org/conda-forge/
packaging      25.0           pyh29332c3_1      61.0 KiB    conda  https://conda.anaconda.org/conda-forge/

This still leaves size somewhat difficult to visually inspect: i believe rattler-build now makes "sizes over some threshhold" a different color, but this approach (or any bold/color) can get lost in logs. I'm not sure how to encode this, as my one ASCII proposal was not well-received.

Another example of data loss is the (useful) direct/transitive dependency status, with a direct dependency encoded as a bold, green package name. Perhaps a depth field (if easy) would be even more useful, especially if direct dependencies were omitted entirely.

depth   name           version        build                 size    kind   source
    4   openssl        3.6.0          h26f9b46_0         3.0 MiB    conda  https://conda.anaconda.org/conda-forge/
    3   oras-py        0.1.14         pyhd8ed1ab_0      33.6 KiB    conda  https://conda.anaconda.org/conda-forge/
        packaging      25.0           pyh29332c3_1      61.0 KiB    conda  https://conda.anaconda.org/conda-forge/

I added the alignment for size:

Computing the depth is a bit more involved but I added a field for the requested-spec:

The Requested is great, and shows actual information: could get long for some matchspecs out there in the wild, but probably more useful than some tree-walking metric which i've frankly never seen anywhere else, certainly not worth the hustle to dig that up if it's not just lying around.

Again regarding space/noise: I'm not sure how much value the second decimal place provides, but hardly seems worth doing anything about, and certainly would be relevant for the GiB unit.

Works great! My humor is probably broken, but I think this is funny: