On your point about the dependencies, I have them listed in the META.json and .yml:

      "configure" : {
         "requires" : {
            "ExtUtils::Depends" : "0.405",
            "ExtUtils::MakeMaker" : "0"
         }
      },
      "develop" : {
         "requires" : {
            "Devel::PPPort" : "3.23",
            "Pod::Coverage::TrustPod" : "0",
            "Test::More" : "0.88",
            "Test::Pod" : "1.41",
            "Test::Pod::Coverage" : "1.08"
         }
      },
      "runtime" : {
         "requires" : {
            "Carp" : "0",
            "Exporter" : "0",
            "XSLoader" : "0",
            "strict" : "0",
            "warnings" : "0"
         }
      },
      "test" : {
         "requires" : {
            "Scalar::Util" : "0",
            "Test2::Suite" : "0.000139",
            "Test2::V0" : "0",
            "Time::HiRes" : "0"
         }
      }
[download]

Is this more Metacpan's fault for not showing dependencies from phases other than Runtime? or is this sort of fine-grain dependency listing not ready for prime-time?