wavesurfer

v1.3.4

Interactive navigable audio visualization using Web Audio and Canvas

BSD-3-Clause
Latest version published 4 years ago
    npm install wavesurfer
  

Package Health Score

56 / 100
Make sure the packages you're using are safe to use
Secure my Project

Popularity

Small

Weekly Downloads (725)

Download trend
Dependents
72
GitHub Stars
5.39K
Forks
1.19K
Contributors
170

Direct Usage Popularity


The npm package wavesurfer receives a total of 725 downloads a week. As such, we scored wavesurfer popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package wavesurfer, we found that it has been starred 5,394 times, and that 72 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.

Security

No known security issues
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

03/2017

Direct Vulnerabilities

Popular
1.3.4
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular
1.3.4
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

Popular
1.3.4
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
BSD-3-Clause

Security Policy
No

We found a way for you to contribute to the project! Looks like wavesurfer is missing a security policy.


You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

    # Install the Snyk CLI and test your project
npm i snyk -g && snyk test wavesurfer
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive
deprecated

Commit Frequency

Open Issues
235
Open PR
8
Last Release
4 years ago
Last Commit
13 days ago

Further analysis of the maintenance status of wavesurfer 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 wavesurfer 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.

Community

Active
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
170
Funding
No

A good and healthy external contribution signal for wavesurfer project, which invites more than one hundred open source maintainers to collaborate on the repository.

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


Embed Package Health Score Badge

package health: 56/100 package health 56/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
0 Direct
Versions
3
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
Yes

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