That's one way to look at it. Here's another:

I once was a participant in a seminar on testing strategies. The speaker was discussing various ways of allocating testing time. He touched on one strategy which basically went like this:

1. 90% of all usage of Quicken will be in the ledger.
2. 90% of all user perception of our product will be based on the performance of the ledger.
3. Maybe we should focus a larger proportion of our testing of Quicken on the ledger.

This isn't to say that the other 90% of the code shouldn't be tested. But, that which has a greater proportion in consumer perception should be more heavily tested.

This has a direct correlation to open-source development. If a module isn't being downloaded, I should not spend my extremely small amount of time on it. Instead, I should focus where I get the greater bang for the buck.

Yes, Graph::Template may have all sorts of reasons why it isn't being downloaded. But, the fact is that it's not being downloaded (in your example). So, until it is, or I have more free time, it's not a priority.

It's basic triage of development time.