browser-run

v12.0.0

Transform stream that executes JavaScript it receives in a real browser and outputs console output For more information about how to use this package see README

Latest version published 10 months 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

58 / 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
12.0.0 | 09/2023
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
11.0.0 | 05/2022
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
10.1.0 | 04/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
9.0.0 | 01/2021
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
8.0.0 | 07/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
License
MIT
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,418)

Download trend
GitHub Stars
441
Forks
61
Contributors
20

Direct Usage Popularity

Occasionally

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

Based on project statistics from the GitHub repository for the npm package browser-run, we found that it has been starred 441 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
20
Funding
Yes

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


Embed Package Health Score Badge

package health: 58/100 package health 58/100

Maintenance

Inactive

Commit Frequency

Open Issues
13
Open PR
2
Last Release
10 months ago
Last Commit
5 months ago

Further analysis of the maintenance status of browser-run based on released npm versions cadence, the repository activity, and other data points determined that its maintenance is Inactive.

We found that browser-run demonstrates a positive version release cadence with at least one new version released in the past 12 months.

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
>=14

Age
11 years
Dependencies
12 Direct
Versions
74
Install Size
433 kB
Dist-tags
1
# of Files
11
Maintainers
1
TS Typings
No

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