s3

v4.4.0

high level amazon s3 client. upload and download files and directories

MIT
Latest version published over 5 years ago
    npm install s3
  

Package Health Score

50 / 100
  • Popularity
    Recognized
  • Maintenance
    Inactive
  • Security
    Security review needed
  • Community
    Sustainable

Popularity

Recognized
Weekly Downloads (72,217)
Dependents
397
GitHub Stars
981
Forks
279
Contributors
17

The npm package s3 receives a total of 72,217 downloads a week. As such, we scored s3 popularity level to be Recognized.

Based on project statistics from the GitHub repository for the npm package s3, we found that it has been starred 981 times, and that 397 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

Security review needed

Security and license risk for recent versions


Direct Vulnerabilities

4.1.1
4.2.0
4.3.0
4.3.1
4.4.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Indirect Vulnerabilities

4.1.1
4.2.0
4.3.0
4.3.1
4.4.0

License Risks

4.1.1
4.2.0
4.3.0
4.3.1
4.4.0
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L
  • 0
    H
  • 0
    M
  • 0
    L

Security Policy
No
All security vulnerabilities belong to production dependencies of direct and indirect packages.

Snyk detected that the latest version of s3 has a security vulnerability.

We highly advise you to review these security issues.

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 s3 is missing a security policy.

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

Maintenance

Inactive
Commit Frequency
No Recent Commits
Open Issues
106
Merged PR
25
Open PR
21
Last Commit
4 years ago

Further analysis of the maintenance status of s3 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 s3 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
17
Funding
No
License
MIT

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

Package

Node.js Compatibility
>=0.10.20

Age
8 years
Dependencies
9 Direct / 14 Total
Versions
5
Install Size
0 B
Dist-tags
1
# of Files
0
Maintainers
1
TS Typings
No

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

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