CPAN has some cruft, that's for sure. Is there a process for cleanup?

This is a problem faced by all open repositories with a low barrier to entry, such as Python Package Index, RubyGems, GitHub ... even Perl Monks (which has an infamous zombification process - including an option to raise from the dead :).

To encourage authors to cleanup their old cruft on CPAN, Perl has The BackPAN (a complete history of CPAN) from which nothing is ever deleted.

Curating CPAN References

CPAN References

Git References

See Also

Updated: Added References sections.

In reply to Re^3: How do I package a module and related apps for successful upload to cpan (CPAN and Git References) by eyepopslikeamosquito
in thread How do I package a module and related apps for successful upload to cpan by PUCKERING

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.