Functions and files changed by CVE fixes in this repository.
Latest located fix
37 published CVEs have a fix traced to functions in go-vikunja/vikunja, the earliest published in 2026. Those fixes changed 116 distinct functions across 69 files, in 618 patch hunks.
Among the 500 repositories tracked here, go-vikunja/vikunja ranks #121 by the number of CVEs with a located fix.
Functions in go-vikunja/vikunja changed by the most CVE fixes.
Files in go-vikunja/vikunja changed by the most CVE fixes.
How much code a CVE fix in go-vikunja/vikunja changes, with backports counted once.
The most recently published CVEs with a fix located in go-vikunja/vikunja, and the functions each fix changed.
Get an alert for each new go-vikunja/vikunja CVE, with the patched functions and AI-written analysis.
Monitor vikunja CVEsRepositories with a similar number of located CVE fixes.
Common questions about CVE fixes in go-vikunja/vikunja.
Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.
Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.
