copy

v0.3.2

Copy files or directories using globs. For more information about how to use this package see README

Latest version published 5 years ago
License: MIT

Ensure you're using the healthiest npm packages

Snyk scans all the packages in your projects for vulnerabilities and provides automated fix advice

Package Health Score

48 / 100

Explore Similar Packages

Security

Security review needed
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security and license risk for significant versions

All Versions
Version Vulnerabilities License Risk
0.3.2 | 05/2018
Popular
  • 0
    H
  • 0
    M
  • 0
    L
0.2.3 | 06/2016
  • 0
    H
  • 0
    M
  • 0
    L
0.1.3 | 11/2015
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 10/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
No

Is your project affected by vulnerabilities?

Scan your projects for vulnerabilities. Fix quickly with automated fixes. Get started with Snyk for free.

Get started free

Popularity

Recognized

Weekly Downloads (30,770)

Download trend
GitHub Stars
90
Forks
115
Contributors
6

Direct Usage Popularity

TOP 30%

The npm package copy receives a total of 30,770 downloads a week. As such, we scored copy popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package copy, we found that it has been starred 90 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
6
Funding
Yes

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like copy is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
9
Open PR
1
Last Release
5 years ago
Last Commit
5 years ago

Further analysis of the maintenance status of copy based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

An important project maintenance signal to consider for copy is that it hasn't seen any new versions released to npm in the past 12 months, and could be considered as a discontinued project, or that which receives low attention from its maintainers.

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
>=0.10.0

Age
10 years
Dependencies
14 Direct
Versions
14
Install Size
25.8 kB
Dist-tags
1
# of Files
11
Maintainers
2
TS Typings
Yes

copy has more than a single and default latest tag published for the npm package. This means, there may be other tags available for this package, such as next to indicate future releases, or stable to indicate stable releases.