s3rver

v3.7.1

Fake S3 server for node For more information about how to use this package see README

Latest version published 3 years 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

51 / 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
3.7.1 | 10/2021
Popular
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
3.6.1 | 06/2020
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
2.2.9 | 03/2019
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
1.0.3 | 02/2017
  • 0
    C
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
0.0.14 | 04/2016
  • 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

Recognized

Weekly Downloads (88,288)

Download trend
GitHub Stars
553
Forks
148
Contributors
50

Direct Usage Popularity

TOP 30%

The npm package s3rver receives a total of 88,288 downloads a week. As such, we scored s3rver popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package s3rver, we found that it has been starred 553 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
No
Code of Conduct
No
Contributors
50
Funding
No

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


Embed Package Health Score Badge

package health: 51/100 package health 51/100

Maintenance

Inactive

Commit Frequency

No Recent Commits
Open Issues
34
Open PR
20
Last Release
3 years ago
Last Commit
3 years ago

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

Package

Node.js Compatibility
>=8.3.0

Age
9 years
Dependencies
11 Direct
Versions
46
Install Size
136 kB
Dist-tags
1
# of Files
26
Maintainers
3
TS Typings
Yes

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