CPAN-API/metacpan-web — comment on commit 40c7daaad84469b6cca83cf2e5a5b4af61c618c8
File:  line 0
By rwstauner:

`Template::Toolkit` is an interesting example:
I picked a url out of my browser history and chose `Template::Manual::Variables` (which is pod not pm).

So the reverse deps link for the module is empty.
However the dist name is `Template-Toolkit` (there is also pod for `Template::Toolkit`)
even though the main module is actually just `Template`.
So the rev deps link for the release is also almost empty (surprisingly there was 1 entry).
Changing the rdeps link manually to point to `Template` and there are now a ton.

`LWP::UserAgent` is a better example:
linking to the module (`LWP::UserAgent`) is exactly what someone would want.
Linking to the release (`libwww-perl`) is not (no results).

So I think the best solution would be to indeed link to both the shown module and the main module,
and if we could ever improve heuristics for the "main" module that would make it even better.