history

v5.0.0

Manage session history with JavaScript

MIT
Latest version published 4 months ago
    npm install history
  

Package Health Score

72 / 100
  • Popularity
    Key ecosystem project
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Key ecosystem project
Weekly Downloads (4,348,360)
Dependents
5.33K
GitHub Stars
6.64K
Forks
754
Contributors
61

The npm package history receives a total of 4,348,360 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 6,644 times, and that 5,334 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 recent versions


Direct Vulnerabilities

5.0.0-beta.6
5.0.0-beta.7
5.0.0-beta.8
5.0.0-beta.9
5.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

5.0.0-beta.6
5.0.0-beta.7
5.0.0-beta.8
5.0.0-beta.9
5.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

5.0.0-beta.6
5.0.0-beta.7
5.0.0-beta.8
5.0.0-beta.9
5.0.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

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 history is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test history
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
Open Issues
66
Merged PR
151
Open PR
18
Last Commit
4 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 Inactive.

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.

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
61
Funding
No
License
MIT

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.

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
1 Direct / 2 Total
Versions
5
Install Size
57.5 kB
Dist-tags
2
# of Files
21
Maintainers
1
TS Typings
Yes

We detected a total of 2 direct & transitive dependencies for history. See the full dependency tree of history

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.