copy-file

v11.0.0

Copy a file For more information about how to use this package see README

Latest version published 12 months 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

66 / 100

Explore Similar Packages

Security

No known security issues
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
11.0.0 | 11/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.1 | 06/2012
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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 (39,502)

Download trend
GitHub Stars
121
Forks
22
Contributors
20

Direct Usage Popularity


The npm package copy-file receives a total of 39,502 downloads a week. As such, we scored copy-file popularity level to be Recognized.

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

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
Yes
Contributors
20
Funding
Yes

With more than 10 contributors for the copy-file repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 66/100 package health 66/100

Maintenance

Inactive

Commit Frequency

Open Issues
2
Open PR
0
Last Release
12 months ago
Last Commit
12 months ago

Further analysis of the maintenance status of copy-file 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-file 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
>=18

Age
12 years
Dependencies
2 Direct
Versions
3
Install Size
14.2 kB
Dist-tags
1
# of Files
7
Maintainers
1
TS Typings
No

copy-file 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.