polyserve

v0.27.15

A simple dev server for bower components For more information about how to use this package see README

Latest version published 4 years ago
License: BSD-3-Clause

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

51 / 100

Security

Security review needed
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
0.27.15 | 01/2019
Popular
  • 0
    H
  • 0
    M
  • 0
    L
0.26.0 | 03/2018
  • 0
    H
  • 0
    M
  • 0
    L
0.25.3 | 03/2018
  • 0
    H
  • 0
    M
  • 0
    L
0.24.0 | 02/2018
  • 0
    H
  • 0
    M
  • 0
    L
0.23.0 | 10/2017
  • 0
    H
  • 0
    M
  • 0
    L
License
BSD-3-Clause
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 (6,631)

Download trend
Dependents
4
GitHub Stars
411
Forks
204
Contributors
170

Direct Usage Popularity

TOP 30%

The npm package polyserve receives a total of 6,631 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 411 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.

Community

Sustainable
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: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

Open Issues
715
Open PR
48
Last Release
4 years ago
Last Commit
9 months 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.

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
8 years
Dependencies
34 Direct
Versions
70
Install Size
188 kB
Dist-tags
1
# of Files
67
Maintainers
9
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.