A dependency finding is a reason to investigate and fix an affected package. It is not a record of an attack against your application. Separating those two statements helps you take the finding seriously without treating an advisory match as proof of a breach.
Who this affects
This guide is for developers reviewing dependency findings in a GitHub repository, including teams whose application code was produced with AI coding tools. Start with the package and version in the finding, then identify the matching declaration in your project. Keep the advisory reference with the repair task so reviewers can see which issue the change addresses.
What FixVibe checks
FixVibe repository scans report declared dependency versions that match published OSV advisories. The report includes the package, version, advisory reference and severity. This coverage reads package.json, requirements.txt, Gemfile.lock and go.mod. A connected GitHub repository and an eligible repository-scan plan are required.
OSV maps vulnerability records to package versions or commits. That makes an advisory match useful evidence about a dependency version, rather than evidence of what an attacker has done in your application. S1
What remains unverified
A version match does not establish whether your application uses the vulnerable code path. It also does not establish that a running deployment contains the same dependency version.
For npm projects, FixVibe reads the version declared in package.json; the version resolved in a lockfile can differ. Compare the finding with your installed dependency tree and lockfile before deciding which change to make. Keep that comparison in the repair notes instead of dismissing the advisory or describing the report as a deployment test.
The severity belongs to the reported issue. Decide the urgency for your application by reviewing the advisory's conditions and the affected feature. npm's guidance explicitly includes reviewing mitigating factors and manually investigating findings that cannot be resolved automatically. S2
Example report
This is a synthetic illustration, not a customer finding or a real advisory:
- Package: example-expression-library.
- Declared version: 1.0.0.
- Advisory: a referenced record identifies that version as affected.
- Follow-up: compare the resolved version and examine whether the affected feature accepts untrusted input.
The first three lines describe the dependency evidence. The follow-up remains an investigation task; it is not something this example claims a scanner has verified. Do not use the fictional package or version as upgrade advice.
How to fix it
Read the advisory and package maintainer's guidance before choosing an update. If a fix exists, update the dependency and its lockfile, then test the application. npm warns that some suggested updates can introduce breaking changes. S2
If no suitable update is available, record the remaining risk and investigate the advisory's mitigation options or an alternative dependency. Do not invent a patched version or suppress a finding solely because automated repair was unavailable. Give the repair an owner and record which behavior still needs review.
Verify the result
Run the repository scan again after changing the dependency declaration and lockfile. Check that the specific advisory finding is absent, and review any other findings separately.
Then verify your build and deployment through your normal release checks. An absent advisory match is not proof that the application is secure or that a running deployment received the intended package change. Keep the scan result, dependency change and deployment verification as distinct pieces of evidence. npm also notes that advisory data can change, so a previous clean audit is not a permanent guarantee. S2
When you are ready, connect the repository in FixVibe using an eligible repository-scan plan and run a repository scan. A public URL scan alone does not provide this repository dependency evidence.
