devalue

v5.1.1

Gets the job done when JSON.stringify can't For more information about how to use this package see README

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

82 / 100

Explore Similar Packages

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
5.1.1 | 09/2024
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.3.3 | 04/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.0 | 04/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.3 | 09/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.1 | 08/2022
  • 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

Key ecosystem project

Weekly Downloads (1,404,879)

Download trend
GitHub Stars
2.21K
Forks
59
Contributors
-

Direct Usage Popularity

TOP 10%

The npm package devalue receives a total of 1,404,879 downloads a week. As such, we scored devalue popularity level to be Key ecosystem project.

Based on project statistics from the GitHub repository for the npm package devalue, we found that it has been starred 2,213 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
No
Code of Conduct
No
Contributors
0
Funding
No

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 82/100 package health 82/100

Maintenance

Sustainable

Commit Frequency

Open Issues
21
Open PR
7
Last Release
3 months ago
Last Commit
3 months ago

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

We found that devalue demonstrates a positive version release cadence with at least one new version released in the past 3 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
7 years
Dependencies
0 Direct
Versions
29
Install Size
31.8 kB
Dist-tags
1
# of Files
13
Maintainers
1
TS Typings
No

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