It's a common misconception what CPAN is. CPAN is a distributed archive where users may store perl-related resources for public use. Additionaly there's a little bit of infrastructure around it (a permission system for module namespaces etc.)

Anything else is just an add-on around the core CPAN. search.cpan.org is just a useful view at CPAN, but it must not be the only one . In fact, there's also kobesearch providing an alternative view. There you find a listing of PPM packages for Win32 for every distribution.

And it's quite easy to provide an additional view to CPAN. Recently I wrote the CPAN Testers Matrix because I was not satisfied with the test report presentation on cpantesters.perl.org. Currently it's ennobled by being linked from both search.cpan.org and kobesearch.

I happen also to like the cpanratings. It's usually the first page I am reading each morning.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.