1. Advisor
  2. JavaScript packages
  3. string-fix-broken-named-entities

string-fix-broken-named-entities

v7.0.17

Finds and fixes common and not so common broken named HTML entities, returns ranges array of fixes For more information about how to use this package see README

Latest version published 10 months ago
License: MIT
NPM
GitHub

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

56 / 100

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
7.0.17 | 01/2024
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
6.1.17 | 11/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
5.4.0 | 05/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.1 | 12/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.0.12 | 11/2020
  • 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

Limited

Weekly Downloads (329)

Download trend
GitHub Stars
191
Forks
27
Contributors
-

Direct Usage Popularity

The npm package string-fix-broken-named-entities receives a total of 329 downloads a week. As such, we scored string-fix-broken-named-entities popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package string-fix-broken-named-entities, we found that it has been starred 191 times.

Downloads are calculated as moving averages for a period of the last 12 months, excluding weekends and known missing data points.

Community

Limited
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 string-fix-broken-named-entities is missing a Code of Conduct.

Embed Package Health Score Badge

package health: 56/100 package health 56/100

Maintenance

Inactive

Commit Frequency

Open Issues
10
Open PR
0
Last Release
10 months ago
Last Commit
16 days ago

Further analysis of the maintenance status of string-fix-broken-named-entities based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that string-fix-broken-named-entities 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.

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>=14.18.0
Age
6 years
Dependencies
5 Direct
Versions
167
Install Size
185 kB
Dist-tags
1
# of Files
7
Maintainers
1
TS Typings
Yes

string-fix-broken-named-entities 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.