history-fix

v4.10.4

Manage session history with JavaScript For more information about how to use this package see README

Latest version published 4 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

53 / 100

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
4.10.4 | 03/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.1 | 08/2019
  • 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

Small

Weekly Downloads (4)

Download trend
GitHub Stars
8.25K
Forks
964
Contributors
70

Direct Usage Popularity


The npm package history-fix receives a total of 4 downloads a week. As such, we scored history-fix popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package history-fix, we found that it has been starred 8,250 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
Yes
Code of Conduct
No
Contributors
70
Funding
No

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

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


Embed Package Health Score Badge

package health: 53/100 package health 53/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
106
Open PR
15
Last Release
4 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of history-fix 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 history-fix 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
not defined

Age
5 years
Dependencies
6 Direct
Versions
6
Install Size
197 kB
Dist-tags
1
# of Files
56
Maintainers
1
TS Typings
Yes

history-fix 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.