obvs.logging.nlogNuGet · C# / .NET
- latest 6.0.21
- stars 338
- assessment attempted 13 days ago
- GitHub evidence observed 13 days ago
- registry checked 14 days ago
- registry ↗
- repository ↗
Vulnerabilities, end of life and next steps
Check a specific version for known advisories, documented mitigations and evidence-backed earlier-version options. Maintenance health is separate from vulnerability status.
Review remediation options →Came back
After 4 years without a release, obvs.logging.nlog published 6.0.21 on 2026-10-25.
Usually this is a maintainer returning. It is also what a hijacked package looks like, so it is worth a glance at what changed before you upgrade.
Maintenance trends
Loading historical repository activity…
Signals · last 2 checks
What the project says about itself
- Open milestones — Obvs 6.0 2/2 done; v7 0/13 done. Source: the repository's milestones.
- OpenSSF Scorecard — 2.9 / 10 on 2026-08-24. Source: OpenSSF, via deps.dev. A third party's view of security practice, not part of the health score.
Third-party facts checked 13 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-25 | first verdict: finished |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/nuget/obvs.logging.nlog)Watch it
Get told when obvs.logging.nlog changes state, changes licence, or is deprecated — instead of finding out during an incident.
Free for up to 25 packages. Signing in is a link sent to your email — there is no password to choose.