libass-wasm

v4.1.0

libass Subtitle Renderer and Parser library for browsers For more information about how to use this package see README

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

62 / 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
4.1.0 | 12/2022
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
4.0.0 | 03/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.1.1 | 08/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.1.0 | 12/2018
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.0 | 10/2018
  • 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 (519)

Download trend
GitHub Stars
366
Forks
142
Contributors
-

Direct Usage Popularity

TOP 30%

The npm package libass-wasm receives a total of 519 downloads a week. As such, we scored libass-wasm popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package libass-wasm, we found that it has been starred 366 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 libass-wasm is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 62/100 package health 62/100

Maintenance

Sustainable

Commit Frequency

Open Issues
18
Open PR
5
Last Release
12 months ago
Last Commit
11 months ago

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

An important project maintenance signal to consider for libass-wasm 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
5 years
Dependencies
0 Direct
Versions
8
Install Size
7.69 MB
Dist-tags
1
# of Files
8
Maintainers
2
TS Typings
No

libass-wasm 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.