libass-wasm

v4.0.0

libass Subtitle Renderer and Parser library for browsers

MIT
Latest version published 2 years ago
    npm install libass-wasm
  

Explore Similar Packages

Package Health Score

61 / 100

Security

No known security issues
Powered by Snyk
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.0.0 | 03/2020
Popular
  • 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.

# Install the Snyk CLI and test your project
npm i snyk -g && snyk test libass-wasm
Get started free

Popularity

Limited

Weekly Downloads (933)

Download trend
Dependents
0
GitHub Stars
279
Forks
78
Contributors
20

Direct Usage Popularity

Uncommon

The npm package libass-wasm receives a total of 933 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 279 times, and that 0 other projects in the ecosystem are dependent on it.

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
20
Funding
No

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


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

Open Issues
11
Open PR
4
Last Release
2 years ago
Last Commit
21 hours 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 Inactive.

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
4 years
Dependencies
0 Direct
Versions
7
Install Size
10.4 MB
Dist-tags
1
# of Files
10
Maintainers
3
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.