history

v5.3.0

Manage session history with JavaScript

MIT
Latest version published 3 months ago
    npm install history
  

Package Health Score

87 / 100

Security

No known security issues
Powered by Snyk
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
5.3.0 | 02/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.2.0 | 12/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.10.1 | 09/2019
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.3.0 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.2.1 | 09/2016
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test history
Get started free

Popularity

Key ecosystem project

Weekly Downloads (12,551,101)

Download trend
Dependents
5.54K
GitHub Stars
7.74K
Forks
946
Contributors
70

Direct Usage Popularity

TOP 5%

The npm package history receives a total of 12,551,101 downloads a week. As such, we scored history popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package history, we found that it has been starred 7,735 times, and that 5,535 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.

Community

Active
Readme.md
Yes
Contributing.md
Yes
Code of Conduct
No
Contributors
70
Funding
No

With more than 10 contributors for the history 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 is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 87/100 package health 87/100

Maintenance

Sustainable

Commit Frequency

Open Issues
99
Open PR
10
Last Release
3 months ago
Last Commit
3 months ago

Further analysis of the maintenance status of history based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Sustainable.

We found that history demonstrates a positive version release cadence with at least one new version released in the past 12 months.

As a healthy sign for on-going project maintenance, we found that the GitHub repository had at least 1 pull request or issue interacted with by the community.

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
1 Direct
Versions
102
Install Size
121 kB
Dist-tags
2
# of Files
21
Maintainers
1
TS Typings
Yes

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