Repository navigation
Advisory re checks
SeriesOfTubez edited this page Nov 15, 2026
·
1 revision
A scan is reused for as long as an app stays at that version. But a vulnerability, or a package found to be malicious, can be published after the scan was made.
So each scan keeps the exact list of packages it resolved, and once a day Barkley asks the advisory database (OSV, through osv-scanner) about those packages again, for every installed version and every update waiting. This takes seconds: the app's code is not fetched or scanned again, and GitHub is not asked anything.
- Nothing changed: you hear nothing. The app's page notes when advisories were last asked.
- Something changed: the result is stored as a new entry. The earlier entry stays in the history exactly as it was. The score is worked out again by the same rules, and you get a notification with the old and new score, counts of what changed, and a link to the comparison.
- OSV can't be reached: nothing changes, and Barkley tries again an hour later. An unreachable service is never treated as a result.
Check advisories again on an app's page does the same on request. It is offered on the newest finished scan of a version made by the current version of Barkley.