File::Copy::Recursive

Perl extension for recursively copying files and directories

Latest version: 0.45 registry icon
Maintenance score
0
Safety score
0
Popularity score
7
Check your open source dependency risks. Get immediate insight about security, stability and licensing risks.
Security
  Vulnerabilities
Version Suggest Low Medium High Critical
0.45 0 0 0 0 0
0.44 0 0 0 0 0
0.43 0 0 0 0 0
0.42 0 0 0 0 0
0.41 0 0 0 0 0
0.40 0 0 0 0 0
0.39 0 0 0 0 0
0.38 0 0 0 0 0
0.37 0 0 0 0 0
0.36 0 0 0 0 0
0.35 0 0 0 0 0
0.34 0 0 0 0 0
0.33 0 0 0 0 0
0.32 0 0 0 0 0
0.31 0 0 0 0 0
0.30 0 0 0 0 0
0.29 0 0 0 0 0
0.28 0 0 0 0 0
0.27 0 0 0 0 0
0.26 0 0 0 0 0
0.25 0 0 0 0 0
0.24 0 0 0 0 0
0.23 0 0 0 0 0
0.22 0 0 0 0 0
0.21 0 0 0 0 0
0.20 0 0 0 0 0
0.19 0 0 0 0 0
0.18 0 0 0 0 0
0.17 0 0 0 0 0
0.16 0 0 0 0 0
0.15 0 0 0 0 0
0.14 0 0 0 0 0
0.13 0 0 0 0 0
0.12 0 0 0 0 0
0.11 0 0 0 0 0
0.10 0 0 0 0 0
0.09 0 0 0 0 0
0.08 0 0 0 0 0
0.07 0 0 0 0 0
0.06 0 0 0 0 0
0.05 0 0 0 0 0
0.04 0 0 0 0 0
0.03 0 0 0 0 0
0.02 0 0 0 0 0
0.01 0 0 0 0 0

Stability
Latest release:

0.45 - This version may not be safe as it has not been updated for a long time. Find out if your coding project uses this component and get notified of any reported security vulnerabilities with Meterian-X Open Source Security Platform

Licensing

Maintain your licence declarations and avoid unwanted licences to protect your IP the way you intended.

Artistic-1.0   -   Artistic License 1.0

Not a wildcard

Not proprietary

OSI Compliant


GPL-1.0-or-later   -   GNU General Public License v1.0 or later

Not a wildcard

Not proprietary

OSI Compliant



File::Copy::Recursive round 2

I have gotten much love from this module but it has suffered from neglect. Partly because I am busy and partly that the code is crusty (it was done back when package globals were all the rage–those of you with CGI tatoos know what I am talking about ;)).

So I am finally making a plan to give this the attention it deserves.

Goals

  1. Fix the RTs and write tests (Issue #3) (pull requests welcome!)
  2. Modernize the code and interface–Issue #2
  3. Do not break existing consumers of the legacy interface–Issue #1