Is Log4Net Oldkey Safe?

Log4Net Oldkey — Nerq Trust Score 53.2/100 (C- grade). Based on analysis of 2 trust dimensions, it is has notable safety concerns. Last updated: 2026-04-02.

Use Log4Net Oldkey with some caution. Log4Net Oldkey is a NuGet package with a Nerq Trust Score of 53.2/100 (C-), based on 3 independent data dimensions. It is below the recommended threshold of 70. Security: 90/100. Popularity: 0/100. Data sourced from nuget.org, GitHub, and NVD. Last updated: 2026-04-02. Machine-readable data (JSON).

Is Log4Net Oldkey safe?

CAUTION — Log4Net Oldkey has a Nerq Trust Score of 53.2/100 (C-). It has moderate trust signals but shows some areas of concern that warrant attention. Suitable for development use — review security and maintenance signals before production deployment.

Security Analysis → {name} Privacy Report →

What is Log4Net Oldkey's trust score?

Log4Net Oldkey has a Nerq Trust Score of 53.2/100, earning a C- grade. This score is based on 2 independently measured dimensions including security, maintenance, and community adoption.

Security
90
Popularity
0

What are the key security findings for Log4Net Oldkey?

Log4Net Oldkey's strongest signal is security at 90/100. No known vulnerabilities have been detected. It has not yet reached the Nerq Verified threshold of 70+.

Security score: 90/100 (strong)
Popularity: 0/100 — community adoption

What is Log4Net Oldkey and who maintains it?

AuthorApache Software Foundation
Categorynuget
SourceN/A

Log4Net Oldkey Across Platforms

Same developer/company in other registries:

ASF.apache-netbeans-java
78/100 · vscode
apache-beam
77/100 · pypi
apache-flink
73/100 · pypi
apache-airflow-providers-qubole
72/100 · pypi
avro
71/100 · gems

Similar Nuget by Trust Score

SFA.DAS.Http (62)BlazorInputFile (62)Microsoft.KernelMemory.MemoryDb.Redis (62)Serilog.Exceptions.Grpc (62)3Chum.IdentityServer4.AccessTokenValidation (62)
See all safest Nuget →

Compare

Log4Net Oldkey vs SFA.DAS.HttpLog4Net Oldkey vs BlazorInputFileLog4Net Oldkey vs Microsoft.KernelMemory.MemoryDb.Redis

Safety Guide: Log4Net Oldkey

What is Log4Net Oldkey?

Log4Net Oldkey is a NuGet package — 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 locat.

How to Verify Safety

Run dotnet list package --vulnerable. Check publisher on nuget.org.

You can also check the trust score via API: GET /v1/preflight?target=log4net-oldkey

Key Safety Concerns for NuGet packages

When evaluating any NuGet package, watch for: dependency vulnerabilities, publisher verification.

Trust Assessment

Log4Net Oldkey has a Nerq Trust Score of 53/100 (C-) and has not yet reached Nerq trust threshold (70+). This score is based on automated analysis of security, maintenance, community, and quality signals.

Key Takeaways

Frequently Asked Questions

Is Log4Net Oldkey safe to use?
Use with some caution. log4net-oldkey has a Nerq Trust Score of 53.2/100 (C-). Strongest signal: security (90/100). Score based on security (90/100), popularity (0/100).
What is Log4Net Oldkey's trust score?
log4net-oldkey: 53.2/100 (C-). Score based on: security (90/100), popularity (0/100). Scores update as new data becomes available. API: GET nerq.ai/v1/preflight?target=log4net-oldkey
What are safer alternatives to Log4Net Oldkey?
In the nuget category, more NuGet packages are being analyzed — check back soon. log4net-oldkey scores 53.2/100.
Does Log4Net Oldkey have known vulnerabilities?
Nerq checks Log4Net Oldkey against NVD, OSV.dev, and registry-specific vulnerability databases. Current security score: 90/100. Run your package manager's audit command for the latest findings.
Is Log4Net Oldkey's publisher verified?
Log4Net Oldkey has a trust score of 53.2/100 (C-). Below Nerq Verified threshold — conduct additional review.
API: /v1/preflight Trust Badge API Docs

Disclaimer: Nerq trust scores are automated assessments based on publicly available signals. They are not endorsements or guarantees. Always conduct your own due diligence.

We use cookies for analytics and caching. Privacy Policy