Analyzed
about 1 month
ago.
based on code collected
2 months
ago.
Project Summary
Access other storage backends via the S3 API
In a Nutshell, s3-proxy...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with increasing Y-O-Y commits -
...
took an estimated 4 years of effort (COCOMO model)
starting with its first commit in July, 2014
ending with its most recent commit 3 months ago
Quick Reference
https://github.com/gaul/s3proxy
Apache License 2.0
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Sub-License
Private Use
Use Patent Claims
Forbidden
Hold Liable
Use Trademarks
Required
Include Copyright
State Changes
Include License
Include Notice
These details are provided for information only. No information here is legal advice and should not be used as such.
Project Security
Vulnerabilities per Version ( last 10 releases )
There are no reported vulnerabilities
Project Vulnerability Report
Security Confidence Index
Poor security track-record
Favorable security track-record
Vulnerability Exposure Index
Many reported vulnerabilities
Few reported vulnerabilities
Did You Know...
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
anyone with an Open Hub account can update a project's tags
-
...
use of OSS increased in 65% of companies in 2016
-
...
you can embed statistics from Open Hub on your site
30 Day SummaryJan 1 2025 — Jan 31 2025
|
12 Month SummaryJan 31 2024 — Jan 31 2025
|
