fclone

v1.0.11

Clone objects by dropping circular references

MIT
Latest version published 5 years ago
    npm install fclone
  

Package Health Score

68 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Popular

Weekly Downloads (526,285)

Download trend
Dependents
47
GitHub Stars
58
Forks
10
Contributors
5

Direct Usage Popularity

TOP 10%

The npm package fclone receives a total of 526,285 downloads a week. As such, we scored fclone popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package fclone, we found that it has been starred 58 times, and that 47 other projects in the ecosystem are dependent on it.

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

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

01/2017

Direct Vulnerabilities

Popular
1.0.11
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.0.11
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.0.11
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
MIT

Security Policy
No

We found a way for you to contribute to the project! Looks like fclone is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test fclone
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
0
Open PR
0
Last Release
5 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of fclone 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 fclone 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.

Community

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

This project has seen only 10 or less contributors.


Embed Package Health Score Badge

package health: 68/100 package health 68/100

Package

Node.js Compatibility
not defined

Age
5 years
Dependencies
0 Direct
Versions
12
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

fclone 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.