Analyzed
about 1 year
ago.
based on code collected
about 1 year
ago.
Project Summary
A replacement for POSIX functions whose behaviour isn’t consistent across *NIX flavours
In a Nutshell, libFixPOSIX...
- ...
- ...
- ...
-
...
took an estimated 1 years of effort (COCOMO model)
starting with its first commit in July, 2010
ending with its most recent commit almost 2 years ago
Quick Reference
https://github.com/sionescu/libf...
Boost Software License
Permitted
Forbidden
Required
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
-
...
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
-
...
data presented on the Open Hub is available through our API
30 Day SummaryDec 21 2023 — Jan 20 2024
|
12 Month SummaryJan 20 2023 — Jan 20 2024
|
Static Analysis ( Generated by Coverity Scan for sionescu/libfixposix )
Repository URL: https://github.com/sionescu/libfixposix
Version: 2f4e8e3
- 2022-11-13
- Last Analyzed
- 15,675
- Lines of Code Analyze
- 0.0
- Defect Density
Defects by status for current build
- 7
- Total defects
- 0
- Outstanding
- 6
- Fixed
CWE Top 25 defects
No top 25 CWE defects were found.