Unfortunately no, there are factors outside of the script that come into play. Althought, I can't disclose a lot about the particular project, but the script 'analyzes' certain websites and indexes data in the database (in a dozen specially designed tables).

I agree with you on that rapid development may leave a number of holes uncovered. Althought, this being a 'throw-away' script (ment to run once and may be easily discarded once the job is done), any possibility of a break in security etc. is minimized ;). However, I too feel somewhat uneasy whenever I have to do a job like that ;/.

In my experience there's no such thing as a throw-away script. They always find a way to stick around until long after they were supposed to be discarded. A little extra planning and testing can save you a lot of time down the road (consider why you use strict).

any possibility of a break in security etc. is minimized

A security policy requiring basic security practices for all scripts should be followed even when deadlines are rushed. Placing a CGI script online without basic measures like taint checking (yes, that's an oversimplification, I know) should not be allowed to happen. Security is a tradeoff, but basic checks are almost always worth it.

Althought, this being a 'throw-away' script (ment to run once and may
be easily discarded once the job is done)

ROTFLMAO :-) Please, Please, Please return to this thread and follow up
when management inevitably asks you to add to, modify, or otherwise maintain
this "throw-away" script. I'll be conservative and bet on 3 months or
less, but I wouldn't be surprised if it happened before the first week-long
run is even over :-)