dotnet-user-secretsNuGet · C# / .NET
- latest 2.2.0
- stars 38,518
- assessment attempted today
- GitHub evidence observed today
- registry checked 18 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 →Moved
The registry still points at aspnet/dotnettools, which is archived with a note saying development moved to aspnet/AspNetCore. The verdict above is about the new home.
Maintenance trends
Loading historical repository activity…
Signals · last 19 checks
What the project says about itself
- Security policy — published. Source: the repository.
- Open milestones — Backlog 2168/5165 done; Infrastructure 29/40 done; Test failures 865/906 done; 8.0.x 44/49 done; 9.0.x 23/28 done. Source: the repository's milestones.
- OpenSSF Scorecard — 6.7 / 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 18 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-11-14 | first verdict: abandoned |
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/nuget/dotnet-user-secrets)Watch it
Get told when dotnet-user-secrets 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.