Why your analysis lives in Git
Vulnlog keeps your analysis in a file in your Git repository, next to the code it’s about. You can keep using an issue tracker or a vulnerability management platform alongside it. Git suits the analysis because an assessment has a fixed structure, belongs next to the code, changes over time, and deserves a review.
A vulnerability assessment has its own shape
An issue tracker is built for work items: a title, a description, an assignee, and a status. A vulnerability assessment needs more structure than that. It names the releases and packages it applies to, the sources that reported it, a verdict with a justification or a severity, and the release that fixes it. In an issue tracker, most of this ends up in free text or in custom fields that each team defines differently, and no tool can read it reliably.
The Vulnlog format has a field for each of these. Because the structure is fixed, Vulnlog can check an entry for mistakes and generate suppression files, reports, and OpenVEX documents from it. OpenVEX documents tell your customers' tools whether a release is affected by a vulnerability.
The analysis stays next to the code
To analyse a vulnerability, you read your code and your dependencies. With the Vulnlog file in the same repository, you record the result in the same place, in the same editor, and with the same tools. You don’t copy findings into another system or switch between your code and a ticket.
The file also travels with the code.
Every clone contains your assessments.
You can read them offline, and they don’t depend on a server or an account.
Each release line can have its own Vulnlog file, so a vulnerability can be affected in one line and not affected in another.
Assessments change over time
An assessment is rarely final. You learn more about how a vulnerability can be exploited, the code that uses the dependency changes, or a customer asks about a deployment you hadn’t considered. The Spring4Shell entry in Acme Shop is an example: the team judged the risk to be medium, and planned the fix for 4.4.0 together with the Spring Boot update. If the published exploit changes, that judgement changes too.
Git records each of these changes. The history shows what the analysis said before, who changed it, when, and in the commit message, why. The file itself stays short because it only holds the current conclusion.
Pull requests add a second reviewer
A verdict of not affected or a suppress block silences a scanner.
That’s a security assessment, and it deserves a second opinion.
When you change an entry in a pull request, another person reviews the analysis before it takes effect, with the same process and the same branch protection you use for code.
The pull request records who approved the change.
Working with an issue tracker
An issue tracker still has its place for planning.
The fix for Spring4Shell can be planned in Jira, with the ticket linked in resolution.ref.
For how Vulnlog compares with platforms such as OWASP Dependency-Track, see Where Vulnlog fits.
As a result, a change to an assessment goes through the same pull requests, reviews, and history as a change to the code. The commit message is where the reason for the change is kept.