Vulnerability Database · Go · Package report
github.com/nrdcg/desec: vulnerability history, versions and safety
github.com/nrdcg/desec is a package in the Go ecosystem. Vulert holds no vulnerabilities for it yet.
Nothing recorded for this package in the Go ecosystem.
Every vulnerability has a patched version to move to.
No published version shipped hostile code.
Vulert verdict on github.com/nrdcg/desec v0.11.3 i
Updated on 23 Oct 2026
Good news: v0.11.3, the version you would install today, has no known vulnerabilities.
- Security Minor issues
- Maintenance Sustainable
- Popularity Little adoption
- Community Inactive
What to do: Stay on v0.11.3 or newer. This can change: a vulnerability disclosed tomorrow can affect v0.11.3 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →
- Current release v0.11.3 — unaffected i
- Vulnerabilities on record 0 i
- Highest CVSS n/a i
- With no published fix 0 i
- Stars 18 i
- OpenSSF scorecard 3/10 i
- Last release this month i
- Licence MPL-2.0 i
Version list, release dates, licence and dependants published by the Go module proxy, refreshed 23 Oct 2026. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Versions
Which versions are affected
Every version Vulert tracks for github.com/nrdcg/desec, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.
- v0.11.3 09 Oct 2026
- v0.11.2 28 Apr 2026
- v0.11.1 29 Oct 2025
- v0.11.1-0.20250328232901-da2099d481a3 28 Mar 2025
- v0.11.0 28 Mar 2025
- v0.10.1-0.20250327213739-8cd348c928ef 27 Mar 2025
- v0.10.0 26 Nov 2024
- v0.9.1-0.20241126171112-7be4d6528eef 26 Nov 2024
- v0.9.0 26 Nov 2024
- v0.8.1-0.20241126155028-03b902e055ca 26 Nov 2024
- v0.8.1-0.20241126154243-ddcd82a73c32 26 Nov 2024
- v0.8.1-0.20240624222509-becdd4a0bc49 24 Jun 2024
- v0.8.1-0.20240624221706-81ea21f4dd85 24 Jun 2024
- v0.8.1-0.20240512013134-a5cb8f95f477 12 May 2024
- v0.7.1-0.20240415001952-4096c93e3936 15 Apr 2024
- v0.8.0 15 Apr 2024
- v0.7.1-0.20240207210757-b27fcb3a808c 07 Feb 2024
- v0.7.1-0.20230223091153-f63bb9048bfc 23 Feb 2023
- v0.7.0 13 Nov 2022
- v0.0.0-20210825032110-401c94cfb8e8 25 Aug 2021
- v0.5.1-0.20210825032110-401c94cfb8e8 25 Aug 2021
- v0.6.0 25 Aug 2021
- v0.5.1-0.20210808112200-063e1baedebf 08 Aug 2021
- v0.5.1-0.20201228210750-b4c3e4ad1d4e 28 Dec 2020
- v0.5.1-0.20201205011012-9bc729ec799e 05 Dec 2020
- v0.5.0 26 Aug 2020
- v0.4.0 26 Aug 2020
- v0.3.0 15 May 2020
- v0.2.0 15 May 2020
- v0.1.0 13 May 2020
- v0.0.0-20200513230624-0eccd748a8de 13 May 2020
All 31 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.
02 Disclosure history
How often vulnerabilities are recorded
No dated vulnerabilities are recorded for this package yet.
03 Vulnerabilities
Recorded vulnerabilities for github.com/nrdcg/desec
No vulnerabilities match this view.
Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback
Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315
Questions
About github.com/nrdcg/desec
Is github.com/nrdcg/desec safe to use?
Vulert has no vulnerabilities on record for github.com/nrdcg/desec in Go at this point. That is a good signal rather than a guarantee: new vulnerabilities are published for packages all the time, so the versions you actually run are still worth monitoring.
What is github.com/nrdcg/desec's Vulert package health score?
Vulert scores github.com/nrdcg/desec 67/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).
Is the latest version of github.com/nrdcg/desec affected?
No. v0.11.3, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.
Which version of github.com/nrdcg/desec should I use?
v0.11.3 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.
How many vulnerabilities does github.com/nrdcg/desec have?
0 vulnerabilities are recorded for github.com/nrdcg/desec in the Go ecosystem: 0 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.
How often are new github.com/nrdcg/desec vulnerabilities disclosed?
0 vulnerabilities were recorded for github.com/nrdcg/desec in the last 12 months. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.
Which versions of github.com/nrdcg/desec are affected?
Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.
How do I monitor github.com/nrdcg/desec for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the github.com/nrdcg/desec version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.