saxes

v6.0.0

An evented streaming XML parser in JavaScript For more information about how to use this package see README

Latest version published 3 years ago
License: ISC

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

73 / 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
6.0.0 | 11/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.0.1 | 04/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.2 | 10/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.1.11 | 06/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.0 | 08/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
ISC
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

Influential project

Weekly Downloads (20,048,203)

Download trend
GitHub Stars
73
Forks
19
Contributors
40

Direct Usage Popularity

TOP 5%

The npm package saxes receives a total of 20,048,203 downloads a week. As such, we scored saxes popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package saxes, we found that it has been starred 73 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
40
Funding
No

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


Embed Package Health Score Badge

package health: 73/100 package health 73/100

Maintenance

Inactive

Commit Frequency

Open Issues
8
Open PR
17
Last Release
3 years ago
Last Commit
3 months ago

Further analysis of the maintenance status of saxes 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 saxes 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
>=v12.22.7

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

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