Analyzed
1 day
ago.
based on code collected
2 days
ago.
In a Nutshell, lnav...
- ...
- ...
-
...
has a well established, mature codebase
maintained by a large development team
with stable Y-O-Y commits -
...
took an estimated 129 years of effort (COCOMO model)
starting with its first commit in September, 2009
ending with its most recent commit 2 days ago
Quick Reference
https://github.com/tstack/lnav
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
-
...
learn about Open Hub updates and features on the Open Hub blog
-
...
nearly 1 in 3 companies have no process for identifying, tracking, or remediating known open source vulnerabilities
-
...
data presented on the Open Hub is available through our API
30 Day SummarySep 18 2026 — Oct 18 2026
|
12 Month SummaryOct 18 2025 — Oct 18 2026
|
Static Analysis ( Generated by Coverity Scan for tstack/lnav )
Repository URL: https://github.com/tstack/lnav
Version: 6538675d15aa9d748047a48cfc830a31bea2a15d
- 2024-06-19
- Last Analyzed
- 457,750
- Lines of Code Analyze
- 1.59
- Defect Density
Defects by status for current build
- 1,007
- Total defects
- 602
- Outstanding
- 382
- Fixed
CWE Top 25 defects
| ID | CWE-Name | Number of Defects |
|---|---|---|
| 120 | Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') | 4 |