Analyzed
1 day
ago.
based on code collected
1 day
ago.
Project Summary
upset calendaring thingy
In a Nutshell, upset...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in February, 2010
ending with its most recent commit over 13 years ago
Quick Reference
https://github.com/dylanwh/upset
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
-
...
anyone with an Open Hub account can update a project's tags
-
...
in 2016, 47% of companies did not have formal process in place to track OS code
-
...
search using multiple tags to find exactly what you need
30 Day SummaryApr 22 2025 — May 22 2025
|
12 Month SummaryMay 22 2024 — May 22 2025
|
