Analyzed
about 8 hours
ago.
based on code collected
about 8 hours
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 over 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...
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
data presented on the Open Hub is available through our API
30 Day SummaryJun 26 2025 — Jul 26 2025
|
12 Month SummaryJul 26 2024 — Jul 26 2025
|
