1. Advisor
  2. JavaScript packages
  3. browser-stink

browser-stink

v1.0.0

Live CSS Reload & Browser Syncing For more information about how to use this package see README

Latest version published 5 years ago
License: Apache-2.0
NPM
GitHub

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

52 / 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
1.0.0 | 01/2020
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
Apache-2.0
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 (1)

Download trend
GitHub Stars
12.2K
Forks
757
Contributors
90

Direct Usage Popularity

The npm package browser-stink receives a total of 1 downloads a week. As such, we scored browser-stink popularity level to be Small.

Based on project statistics from the GitHub repository for the npm package browser-stink, we found that it has been starred 12,195 times.

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
Yes
Code of Conduct
No
Contributors
90
Funding
No

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

Embed Package Health Score Badge

package health: 52/100 package health 52/100

Maintenance

Inactive

Commit Frequency

Open Issues
541
Open PR
31
Last Release
5 years ago
Last Commit
3 months ago

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

Keep your project healthy

scan-reversed

Check your package.json

NEW
Ensure all the packages you're using are healthy and well-maintained
arrow
intellij

Snyk Vulnerability Scanner

external
Get health score & security insights directly in your IDE
arrow

Package

Node.js Compatibility
>= 6.0.0
Age
5 years
Dependencies
30 Direct
Versions
2
Install Size
563 kB
Dist-tags
1
# of Files
131
Maintainers
1
TS Typings
No

browser-stink 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.