liblogging

I Use This!

Inactive

Analyzed about 21 hours ago. based on code collected 1 day ago.

Project Summary

Liblogging is an easy to use library for logging. Among others, it offers an enhanced replacement for the syslog() call, but retains its ease of use. This new call is both signal- and thread-safe and can log to multiple destinations concurrently.

In a Nutshell, liblogging...

...
has had 208 commits made by 13 contributors
representing 27,689 lines of code
...
is mostly written in C
with a very well-commented source code
...
has a well established, mature codebase
maintained by nobody
with stable Y-O-Y commits
...
took an estimated 7 years of effort (COCOMO model)
starting with its first commit in September, 2003
ending with its most recent commit about 6 years ago

Quick Reference

Project Links:

Homepage
Download
Issue Trackers

Code Locations:

https://github.com/rsyslog/liblo...

Similar Projects:

Managers:

Rainer Gerhards

Licenses

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.

All Licenses

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

About Project Vulnerability Report

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
...
compare projects before you chose one to use