playmusic

v2.3.0

Node JS Google Play Music API. Supports All Access For more information about how to use this package see README

Latest version published 7 years ago
License: MPL-2.0

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

45 / 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
2.3.0 | 09/2017
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
2.2.1 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
1.1.1 | 12/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.3.2 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.4.1 | 11/2014
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
License
MPL-2.0
Alert

Non-Permissive License

We noticed that this project uses a license which requires less permissive conditions such as disclosing the source code, stating changes or redistributing the source under the same license. It is advised to further consult the license terms before use.

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 (40)

Download trend
GitHub Stars
317
Forks
60
Contributors
16

Direct Usage Popularity

Uncommon

The npm package playmusic receives a total of 40 downloads a week. As such, we scored playmusic popularity level to be Limited.

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

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

Community

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
16
Funding
No

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


Embed Package Health Score Badge

package health: 45/100 package health 45/100

Maintenance

Inactive
deprecated

Commit Frequency

No Recent Commits
Open Issues
24
Open PR
7
Last Release
7 years ago
Last Commit
7 years ago

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

In the past month we didn't find any pull request activity or change in issues status has been detected for the GitHub repository.

Package

Node.js Compatibility
not defined

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

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