1. Advisor
  2. JavaScript packages
  3. fill-keys

fill-keys

v2.0.0

Fill keys in a destination that are defined on the source For more information about how to use this package see README

Latest version published 2 years ago
License: MIT
NPM
GitHub

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

62 / 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
2.0.0 | 10/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.2 | 10/2015
Popular
  • 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

Popular

Weekly Downloads (684,161)

Download trend
GitHub Stars
0
Forks
1
Contributors
4

Direct Usage Popularity

TOP 30%

The npm package fill-keys receives a total of 684,161 downloads a week. As such, we scored fill-keys popularity level to be Popular.

Based on project statistics from the GitHub repository for the npm package fill-keys, we found that it has been starred ? 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
4
Funding
No

This project has seen only 10 or less contributors.

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

Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Inactive

Commit Frequency

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

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

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>= 16
Age
10 years
Dependencies
2 Direct
Versions
5
Install Size
3.23 kB
Dist-tags
1
# of Files
4
Maintainers
1
TS Typings
No

fill-keys 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.