NuGet package

log4net

3.0.4

Default version

Security Advisories

In this package
No direct advisories detected.

Licenses

Learn more about license information.

Licenses

Apache-2.0

Published

Description

log4net is a tool to help the programmer output log statements to a variety of output targets. In case of problems with an application, it is helpful to enable logging so that the problem can be located. With log4net it is possible to enable logging at runtime without modifying the application binary. The log4net package is designed so that log statements can remain in shipped code without incurring a high performance cost. It follows that the speed of logging (or rather not logging) is crucial. At the same time, log output can be so voluminous that it quickly becomes overwhelming. One of the distinctive features of log4net is the notion of hierarchical loggers. Using these loggers it is possible to selectively control which log statements are output at arbitrary granularity. log4net is designed with two distinct goals in mind: speed and flexibility

Owners

  • asf

Links

Origin
Homepage
Repo

Projects

apache/logging-log4net

GitHub

Apache Log4net is a versatile, feature-rich, efficient logging API and backend for .NET

 334 forks
 886 stars

OpenSSF scorecard

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

View information about checks and how to fix failures.

Score
4.8/10
Scorecard as of .
Dangerous-Workflow
10/10
Determines if the project's GitHub Action workflows avoid dangerous patterns.
Reasoning
no dangerous workflow patterns detected
Code-Review
4/10
Determines if the project requires human code review before pull requests (aka merge requests) are merged.
Reasoning
Found 3/7 approved changesets -- score normalized to 4
Token-Permissions
0/10
Determines if the project's workflows follow the principle of least privilege.
Reasoning
detected GitHub workflow tokens with excessive permissions
CII-Best-Practices
0/10
Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.
Reasoning
no effort to earn an OpenSSF best practices badge detected
Maintained
10/10
Determines if the project is "actively maintained".
Reasoning
30 commit(s) and 0 issue activity found in the last 90 days -- score normalized to 10
Binary-Artifacts
9/10
Determines if the project has generated executable (binary) artifacts in the source repository.
Reasoning
binaries present in source code
Fuzzing
0/10
Determines if the project uses fuzzing.
Reasoning
project is not fuzzed
License
10/10
Determines if the project has defined a license.
Reasoning
license file detected
Signed-Releases
8/10
Determines if the project cryptographically signs release artifacts.
Reasoning
5 out of the last 5 releases have a total of 5 signed artifacts.
Branch-Protection
0/10
Determines if the default and release branches are protected with GitHub's branch protection settings.
Reasoning
branch protection not enabled on development/release branches
Security-Policy
10/10
Determines if the project has published a security policy.
Reasoning
security policy file detected
Pinned-Dependencies
2/10
Determines if the project has declared and pinned the dependencies of its build process.
Reasoning
dependency not pinned by hash detected -- score normalized to 2
SAST
0/10
Determines if the project uses static code analysis.
Reasoning
SAST tool is not run on all commits -- score normalized to 0
Vulnerabilities
0/10
Determines if the project has open, known unfixed vulnerabilities.
Reasoning
11 existing vulnerabilities detected

Project metadata as of .