Analyzed
about 6 hours
ago.
based on code collected
about 6 hours
ago.
In a Nutshell, twitter spitball...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in July, 2010
ending with its most recent commit about 6 years ago
Quick Reference
Organization:
https://github.com/twitter/spitball
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
-
...
you can subscribe to e-mail newsletters to receive update from the Open Hub blog
-
...
65% of companies leverage OSS to speed application development in 2016
-
...
by exploring contributors within projects, you can view details on every commit they have made to that project
30 Day SummaryMay 26 2025 — Jun 25 2025
|
12 Month SummaryJun 25 2024 — Jun 25 2025
|
