I tend to be very wary of using code from script sites that are not at least in some way intertwined with CPAN, such as this site. Without a peer review process, it's all-too-common to see "cargo-cult programming" hard at work on these freebie sites, and security vulnerabilities abound.

Perhaps this is an over-generalization, but I've seen one-too-many a security note come across Bugtraq about a script that's been made available on one of these freebie Perl archives. Generally on CPAN, and on sites where code can be reviewed like this one, major problems are caught beforehand.

Note that this also extends to Perl code purchased from an outside vendor. I have dealt with only 3 or 4 major Perl packages aquired in this manner, but they ALL had SERIOUS security problems, which I was thankfully able to patch up, but in all cases it was clear that the developer knew little about the science of programming. Finding a good Perl developer is a very hard thing to do. That is a major reason why Perl is not an official supported language in my company. :)

In reply to Re: Procedure for finding/searching for existing code by Fastolfe
in thread Procedure for finding/searching for existing code by belize

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.