private-beachball

v2.18.0

The Sunniest Semantic Version Bumper 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

61 / 100

Explore Similar Packages

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
2.17.1 | 10/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.18.0 | 10/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
Security Policy
Yes

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

Download trend
Dependents
0
GitHub Stars
563
Forks
72
Contributors
50

Direct Usage Popularity


The npm package private-beachball receives a total of 0 downloads a week. As such, we scored private-beachball popularity level to be Limited.

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

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

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


Embed Package Health Score Badge

package health: 61/100 package health 61/100

Maintenance

Inactive

Commit Frequency

Open Issues
94
Open PR
18
Last Release
1 year ago
Last Commit
3 days ago

Further analysis of the maintenance status of private-beachball 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 private-beachball 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
>=12.0.0

Age
1 year
Dependencies
15 Direct
Versions
4
Install Size
948 kB
Dist-tags
1
# of Files
304
Maintainers
1
TS Typings
No

private-beachball 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.