I'm probably not the only person to write a CPAN module with an unnecessary dependency. In my case, even though the dependency has some peripheral use, admittedly there are ulterior motives. I'm still working out the mechanics of using optional dependencies for optional functionality. Notwithstanding, I think my approach is too sketchy and one concern is that I can get away with it.
The point is: I recently tried to install another module with the same liability. One particular dependency has many other dependencies (A chain of potential Trojan Horses) and the functionality seems irrelevant.
Are there any standard practices that I can refer to? Some way to confirm my suspicions? Ultimately, should I try to sever the unnecessary dependency myself or is there a better approach to achieve the "greater good"?
Thanks- Jim