sandbox

v0.8.6

A nifty javascript sandbox for node.js

ISC
Latest version published 7 years ago
    npm install sandbox
  

Package Health Score

34 / 100

Popularity

Limited

Weekly Downloads (157)

Download trend
Dependents
33
GitHub Stars
780
Forks
116
Contributors
1

Direct Usage Popularity

TOP 30%

The npm package sandbox receives a total of 157 downloads a week. As such, we scored sandbox popularity level to be Limited.

Based on project statistics from the GitHub repository for the npm package sandbox, we found that it has been starred 780 times, and that 33 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 issues found
Powered by Snyk

Security and license risk for significant versions

All Versions
Popular

Version

Release Date

04/2011
06/2014

Direct Vulnerabilities

0.7.0
Popular
0.8.6

Indirect Vulnerabilities

0.7.0
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.8.6
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L

License Risk

0.7.0
  • 0
    H
  • 0
    M
  • 0
    L
Popular
0.8.6
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

License
ISC

Security Policy
No

We found a way for you to contribute to the project! Looks like sandbox 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 sandbox
Keep your project free of vulnerabilities with Snyk

Maintenance

Inactive

Commit Frequency

Open Issues
21
Open PR
9
Last Release
7 years ago
Last Commit
1 day ago

Further analysis of the maintenance status of sandbox 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 sandbox 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

Limited
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
1
Funding
No

This project has seen only 10 or less contributors.

We found a way for you to contribute to the project! Looks like sandbox is missing a Code of Conduct.


Embed Package Health Score Badge

package health: 34/100 package health 34/100

Package

Node.js Compatibility
not defined

Age
10 years
Dependencies
0 Direct
Versions
9
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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