Why Was an Issue Marked as Solved

In Aikido, issues automatically move from Open to Solved when they are no longer detected in the latest scan.

There are several common reasons why this might happen:

✅ The Issue Was Fixed

Someone in your team resolved the problem — it's no longer showing up in the scan because it has been completely removed or fixed in code.

If you're scanning a different branch, Aikido will:

Close issues tied to the old branch
Open any issues found on the new one
💡You can verify which branch is being scanned via the tag on the repository page

If the affected file was moved or renamed, Aikido will:

Sometimes CVEs get updated to narrow down the versions affected.

Example:

If a vulnerable package is moved from a production dependency to a dev-dependency, Aikido will:

Mark the original issue as solved (since the dependency type changed)
Not longer report the issue as dev-dependencies are by default not scanned.
💡 You can enable scanning of dev-dependencies on a per-repository basis. More information in this doc

Static analysis rules are continuously improved to reduce false positives. As these rules become more accurate, Aikido may:

When scanning locally, changing the target directory will influence what gets scanned.

This list covers the most frequent causes, but there may be other edge cases.

👉 If you're unsure why something was marked as solved, just reach out through the in-app chat — we're happy to help.