Analyzed
1 day
ago.
based on code collected
1 day
ago.
Project Summary
Libbpf authoritative source code is developed as part of bpf-next Linux source tree under tools/lib/bpf subdirectory and is periodically synced to Github. As such, all the libbpf changes should be sent to BPF mailing list, please don't open PRs here unless you are changing Github-specific parts of libbpf (e.g., Github-specific Makefile).
In a Nutshell, sudipm-mukherjee/libbpf...
- ...
- ...
- ...
-
...
took an estimated 32 years of effort (COCOMO model)
starting with its first commit in April, 2020
ending with its most recent commit 5 months ago
Quick Reference
https://github.com/sudipm-mukher...
BSD 2-clause "Simplified" License
Permitted
Commercial Use
Modify
Distribute
Place Warranty
Forbidden
Hold Liable
Required
Include Copyright
Include License
These details are provided for information only. No information here is legal advice and should not be used as such.
GNU Library General Public License v2 or later
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...
-
...
there are over 3,000 projects on the Open Hub with security vulnerabilities reported against them
-
...
data presented on the Open Hub is available through our API
-
...
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
30 Day SummaryMar 17 2024 — Apr 16 2024
|
12 Month SummaryApr 16 2023 — Apr 16 2024
|
