polyserve

v0.27.15

A simple dev server for bower components

BSD-3-Clause
Latest version published 3 years ago
    npm install polyserve
  

Package Health Score

54 / 100

Popularity

Small

Weekly Downloads (7,514)

Download trend
Dependents
4
GitHub Stars
405
Forks
201
Contributors
170

Direct Usage Popularity

TOP 30%

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

Based on project statistics from the GitHub repository for the npm package polyserve, we found that it has been starred 405 times, and that 4 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

Security review needed
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

10/2017
02/2018
03/2018
03/2018
01/2019

Direct Vulnerabilities

0.23.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.24.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.25.3
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
0.26.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.27.15
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

Popular

License Risk

0.23.0
  • 0
    H
  • 0
    M
  • 0
    L
0.24.0
  • 0
    H
  • 0
    M
  • 0
    L
0.25.3
  • 0
    H
  • 0
    M
  • 0
    L
0.26.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.27.15
  • 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 polyserve 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 polyserve
Fix it in your project with Snyk!

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
1.11K
Open PR
93
Last Release
3 years ago
Last Commit
2 years ago

Further analysis of the maintenance status of polyserve 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 polyserve 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 polyserve 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 polyserve is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 54/100 package health 54/100

Package

Node.js Compatibility
not defined

Age
7 years
Dependencies
34 Direct
Versions
70
Install Size
188 kB
Dist-tags
1
# of Files
67
Maintainers
11
TS Typings
Yes

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