persist-statelessly

v0.1.4

Seemlessly persist objects to a local file For more information about how to use this package see README

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

60 / 100

Security

Security review needed
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
0.1.4 | 12/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.1.1 | 10/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.2 | 06/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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 (2)

Download trend
GitHub Stars
3.93K
Forks
59
Contributors
30

Direct Usage Popularity


The npm package persist-statelessly receives a total of 2 downloads a week. As such, we scored persist-statelessly popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package persist-statelessly, we found that it has been starred 3,931 times.

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
No
Contributing.md
Yes
Code of Conduct
Yes
Contributors
30
Funding
Yes

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

How about a good first contribution to this project? It seems that persist-statelessly is missing a README file.


Embed Package Health Score Badge

package health: 60/100 package health 60/100

Maintenance

Inactive

Commit Frequency

Open Issues
115
Open PR
1
Last Release
3 years ago
Last Commit
4 days ago

Further analysis of the maintenance status of persist-statelessly 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 persist-statelessly 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.

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
3 years
Dependencies
2 Direct
Versions
8
Install Size
110 kB
Dist-tags
1
# of Files
51
Maintainers
1
TS Typings
No

persist-statelessly 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.