last-one-wins

v1.0.4

Make sure the last sync call to an async function is executed after all previous ones have finished

MIT
Latest version published almost 5 years ago
    npm install last-one-wins
  
We couldn't find any similar packages Browse all packages

Package Health Score

48 / 100
  • Popularity
    Small
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Limited

Popularity

Small
Weekly Downloads (4,242)
Dependents
16
GitHub Stars
32
Forks
2
Contributors
1

The npm package last-one-wins receives a total of 4,242 downloads a week. As such, we scored last-one-wins popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package last-one-wins, we found that it has been starred 32 times, and that 16 other projects on 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

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

1.0.4
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

1.0.4
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

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

Security Policy
No

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

We found a way for you to contribute to the project! Looks like last-one-wins is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test last-one-wins
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
0
Merged PR
0
Open PR
0
Last Commit
5 years ago

Further analysis of the maintenance status of last-one-wins 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 last-one-wins 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
Yes
License
MIT

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Package

Node.js Compatibility
not defined

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

last-one-wins 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.