Source code | Report a bug in this site | Credits | Links

Given a module name, this service will show you its dependencies along with a summary of their test results from the CPAN testers. The idea is that if you have a choice of several modules to use, this will show you which is the most reliable.

Please note: this site is a tool to analyse the dependencies of modules written in the Perl programming language. I can not help you with any problems you might have with using any modules.

It relies on modules having META.yml files so it can work out their dependencies, and is case-sensitive. The perl version number is used to filter test results and also to determine what's a core module and what's not - some core modules also exist seperately on the CPAN, but we don't bother looking at their dependencies. If you choose a version like X.Y as opposed to X.Y.Z, then you'll get test results for all X.Y.* versions, and we assume X.Y.0 for figuring out what's in core. If you choose 'any version', then you get all test results and we divine core modules from perl 5.005. Test results are cached for performance and may be up to three days out of date. Modules can depend on particular versions of other modules. We ignore that. Patches welcome.

This service costs €50 a month to run. If you think it rocks incredibly hard, then I like shiny beads, but wouldn't say no to a little something to help defray costs either.

(Get results in XML)

-	0.	Apache2::Ajax	S B R D			6 PASSes, 0 UNKNOWNs, 1 FAIL, 0 NAs
	1.	Apache2::RequestRec	S B R D			16 PASSes, 51 UNKNOWNs, 92 FAILs, 0 NAs
-	2.	CGI::Ajax	S B R D			241 PASSes, 2 UNKNOWNs, 0 FAILs, 0 NAs
-	3.	Class::Accessor	S B R D			886 PASSes, 0 UNKNOWNs, 2 FAILs, 0 NAs
-	4.	base	S B R D			528 PASSes, 0 UNKNOWNs, 2 FAILs, 0 NAs
-	5.	Test::More	S B R D			798 PASSes, 5 UNKNOWNs, 1 FAIL, 0 NAs
	6.	Test::Harness	S B R D			577 PASSes, 1 UNKNOWN, 13 FAILs, 0 NAs
	7.	ExtUtils::MakeMaker	S B R D			Core module
	8.	CGI	S B R D			Core module
Chance of all tests passing						8.2% (to 1dp) (but note that this doesn't mean much)

The chance of success is calculated by multiplying the probabilities of the module and all its dependencies passing their tests.

code written while listening to

so the bugs are all his fault