microsoft.extensions.configuration.azurekeyvaultNuGet · C# / .NET
- latest 3.1.24
- last known licence Apache-2.0
- stars 3,220
- assessment attempted 13 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 →Maintenance trends
Loading historical repository activity…
Signals · last 1 check
The first observation is recorded. Trend lines appear once at least two checks have data for the same signal.
What the project says about itself
- Security policy — published. Source: the repository.
- Open milestones — Backlog 184/191 done; Data Ingestion Preview 2 16/19 done; 11.0 (due 2026-11-10) 4/8 done; 12.0 (due 2027-11-09) 0/1 done. Source: the repository's milestones.
- OpenSSF Scorecard — 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 13 days ago; registry facts on every crawl.
State history 1
| When | Change |
|---|---|
| 2026-10-12 | first verdict: abandoned |
Where to go instead 1
-
Azure.Extensions.AspNetCore.Configuration.Secrets
Named by the maintainers in the deprecation notice
While this package is still supported, it has been replaced by Azure.Extensions.AspNetCore.Configuration.Secrets per https://github.com/aspnet/Announcements/issues/408. We recommend using that instead.
From the maintainers’ own deprecation notice.
Badge
Drop this in your README. It re-renders itself as the verdict changes.
[](https://isitdeadyet.dev/nuget/microsoft.extensions.configuration.azurekeyvault)Watch it
Get told when microsoft.extensions.configuration.azurekeyvault 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.