peerjs-patch

v1.3.2-0

PeerJS client For more information about how to use this package see README

Latest version published 4 years 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

63 / 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
1.3.2-0 | 03/2021
Popular
  • 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

Small

Weekly Downloads (0)

Download trend
GitHub Stars
12.47K
Forks
1.43K
Contributors
80

Direct Usage Popularity


The npm package peerjs-patch receives a total of 0 downloads a week. As such, we scored peerjs-patch popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package peerjs-patch, we found that it has been starred 12,468 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
No
Code of Conduct
Yes
Contributors
80
Funding
Yes

With more than 10 contributors for the peerjs-patch repository, this is possibly a sign for a growing and inviting community.


Embed Package Health Score Badge

package health: 63/100 package health 63/100

Maintenance

Inactive

Commit Frequency

Open Issues
168
Open PR
22
Last Release
4 years ago
Last Commit
2 months ago

Further analysis of the maintenance status of peerjs-patch 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 peerjs-patch 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
4 Direct
Versions
2
Install Size
1.51 MB
Dist-tags
1
# of Files
24
Maintainers
1
TS Typings
No

peerjs-patch 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.