plyr

v3.7.8

A simple, accessible and customizable HTML5, YouTube and Vimeo media player For more information about how to use this package see README

Latest version published 1 year 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

77 / 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
3.7.8 | 03/2023
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.6.12 | 12/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.0.18 | 11/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.9.0 | 08/2016
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.8.12 | 07/2016
  • 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

Influential project

Weekly Downloads (117,137)

Download trend
GitHub Stars
26.08K
Forks
2.91K
Contributors
180

Direct Usage Popularity

TOP 5%

The npm package plyr receives a total of 117,137 downloads a week. As such, we scored plyr popularity level to be Influential project.

Based on project statistics from the GitHub repository for the npm package plyr, we found that it has been starred 26,078 times.

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

Community

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

A good and healthy external contribution signal for plyr 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 plyr is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 77/100 package health 77/100

Maintenance

Inactive

Commit Frequency

Open Issues
860
Open PR
35
Last Release
1 year ago
Last Commit
26 days ago

Further analysis of the maintenance status of plyr 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 plyr 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
8 years
Dependencies
5 Direct
Versions
160
Install Size
5.3 MB
Dist-tags
1
# of Files
124
Maintainers
1
TS Typings
Yes

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