Yes! If I can have phrased it right. But if I can't - like this time - then I try to gather a lot of comments in hope few of them will be really helpful. If you know another, less nerve-racking way for this - I'll be happy to hear it and to use it in the future.

If badaiaqrandista is right, then why statistics prove different thing?

OK -- deep breath everyone. Hold it. OK, now let it out slowly, and as you do that, feel yourself getter calmer, more relaxed, like you're staring into the shallows of a calm, clear lake on a beautiful cool day.

Now powerman, when someone talks about reputation, this could mean XP (experience points), or it could just be your reputation among the users here at Perlmonks. Because it seems you've been ranting about reliability and security without much to back it up, your reputation (forget about XP for now) has suffered.

This means any posts of yours over the next month or three are going to be viewed with a janudiced eye -- some monks just won't read them, some will read them reluctantly, and some will not be kind -- they'll look for any excuse to criticise your posts.

So, instead of running into the Monastery and immediately sreaming about how crappy the CPAN modules are in terms of reliability and security, here's a different approach: take a module that suffers from those problems, identify the problem areas, offer fixes to the authour or community, and document your process.

Now, ideally you'd take a module that's used a little -- something written five years ago that no one uses wouldn't be a good choice. Something brand new probably isn't a good choice either. So I'd suggest, pick something with some experience and some usage.

And good luck with that.