Analyzed
about 1 month
ago.
based on code collected
about 1 month
ago.
Project Summary
Friend2Friend content distribution system for more or less controlled content distribution.
Possible usage areas include:
* F2F filesharing
* Backend for distributed digital asset delivery
* Distribution of Software updates
* ...
In a Nutshell, BitHorde...
- ...
- ...
- ...
-
...
took an estimated 3 years of effort (COCOMO model)
starting with its first commit in September, 2009
ending with its most recent commit about 4 years ago
Quick Reference
https://github.com/rawler/bithorde
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
-
...
learn about Open Hub updates and features on the Open Hub blog
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
anyone with an Open Hub account can update a project's tags
30 Day SummaryOct 3 2024 — Nov 2 2024
|
12 Month SummaryNov 2 2023 — Nov 2 2024
|
