anywhere

v1.5.0

Run static file server anywhere

MIT
Latest version published almost 3 years ago
    npm install anywhere
  

Package Health Score

48 / 100
  • Popularity
    Limited
  • Maintenance
    Inactive
  • Security
    No known security issues
  • Community
    Sustainable

Popularity

Limited
Weekly Downloads (416)
Dependents
91
GitHub Stars
854
Forks
154
Contributors
6

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

Based on project statistics from the GitHub repository for the npm package anywhere, we found that it has been starred 854 times, and that 91 other projects on 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

No known security issues

Security and license risk for significant versions

All Versions

Direct Vulnerabilities

0.0.9
1.4.0
1.5.0
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

0.0.9
1.4.0
1.5.0
  • 0
    H
  • 0
    M
  • 0
    L

License Risks

0.0.9
1.4.0
1.5.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Security Policy
No

You can connect your project's repository to Snyk to stay up to date on security alerts and receive automatic fix pull requests.

We found a way for you to contribute to the project! Looks like anywhere is missing a security policy.

    # Install the Snyk CLI and test your project
npm i snyk && snyk test anywhere
Fix it in your project with Snyk!

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
2
Merged PR
7
Open PR
2
Last Commit
2 years ago

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

Community

Sustainable
Readme.md
Yes
Contributing.md
No
Code of Conduct
No
Contributors
6
Funding
No
License
MIT

This project has seen only 10 or less contributors.

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


Embed Package Health Score Badge

package health: 48/100 package health 48/100

Package

Node.js Compatibility
not defined

Age
8 years
Dependencies
6 Direct / 36 Total
Versions
3
Install Size
7.69 kB
Dist-tags
1
# of Files
5
Maintainers
1
TS Typings
No

We detected a total of 36 direct & transitive dependencies for anywhere. See the full dependency tree of anywhere

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