Repository navigation
Releases
Limbowatch 0.1.0a22
Limbowatch 0.1.0a22. What changed: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md#010a22-2026-11-19
The image now runs isolated from the runner (the checkout read-only, never the runner's temp directory, workflow commands off while it prints). Breaking (image mode): files that extra-args writes (--state, --audit-log, more -o) go directly in the reports directory, and the image sees nothing outside the checkout.
Limbowatch 0.1.0a21
Limbowatch 0.1.0a21 (alpha). Scans and the tracker are unchanged from 0.1.0a20. New for teams that run Limbowatch standalone: own-feed pipelines that need only the command line, no Limbowatch image (deploy/own-feed/github/limbo-feed-cli.yml and deploy/own-feed/gitlab/.gitlab-ci.cli.yml in limbowatch/limbowatch), and a website organised around every way to run it: https://limbo.watch/scan/standalone/. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a20
Limbowatch 0.1.0a20 (alpha). Scans and the tracker are unchanged from 0.1.0a19. One fix to the own-feed GitLab pipeline (deploy/own-feed in limbowatch/limbowatch): a new feed's first run now reads only the CVE changes since the CVE List export it imported (183 records instead of about 2,280, 8.7 minutes instead of 17). If you build your own feed on GitLab, copy the pipeline file again. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a19
Limbowatch 0.1.0a19 (alpha). Scans are unchanged from 0.1.0a18. For teams building their own feed (deploy/own-feed in limbowatch/limbowatch): the GitLab pipeline now keeps its state between runs (in the project's package registry; before, every run started over), and a new tracker's first run is about 15 minutes shorter. If you build your own feed on GitLab, copy the pipeline file again. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a18
Limbowatch 0.1.0a18 (alpha). The scanner is unchanged from 0.1.0a17. One fix to the own-feed GitHub pipeline (deploy/own-feed in limbowatch/limbowatch): in a private repository on a plan without attestations for private repositories, the run failed before publishing the feed; it now warns and publishes the feed unattested. If you set up your own feed from 0.1.0a17, copy the pipeline file again. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a17
Limbowatch 0.1.0a17 (alpha). For teams that won't take advisory data from limbo.watch: set LIMBOWATCH_FEED: none in the step's env to scan with no feed (each dependency's source repository is read on GitHub during the scan; set a GitHub token), or LIMBOWATCH_FEED: <https URL or directory> to scan against a feed you build yourself with the ready-to-copy pipelines in deploy/own-feed (the whole limbo feed, or one focused on your own projects' dependencies; docs/OWN_FEED.md). Reports and issues name the feed they used. Nothing changes for scans that use the limbo feed, apart from the wording of the "checked by name only" reasons; upgrading is optional. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a16
Limbowatch 0.1.0a16 (alpha). Security fixes from two outside reviews and an independent one. Tokens are never sent over plain http:// to another machine: with an http-only Gitea or Forgejo, issues: now stops and says why; set LIMBOWATCH_ALLOW_INSECURE_HTTP: "1" in the step's env to send the token anyway. Registry lookups from build files can no longer be walked to another repository with ../, and the GitHub token and NVD key go over https only. Fixed: when page 2 or later of a repository's advisories couldn't be read, the first page was taken for the whole list; such a repository is now reported as partly checked. A * or ? in extra-args is passed as typed. The image installs Debian's security updates when it's built (zlib), and large lockfiles are scanned up to 27 times faster. Upgrade from 0.1.0a15 and earlier. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a15
Limbowatch 0.1.0a15 (alpha). The scan now checks that the limbo feed it downloads is genuine before using it: the feed and watchlist must be named, together, by a signed build attestation from limbowatch/limbowatch's site workflow on main, looked up on GitHub. A feed that isn't (swapped on the website, its host, the network or the runner's cache, or an older feed served next to a newer watchlist) is refused and the step fails with a clear error instead of under-reporting. If GitHub can't be reached it warns and goes on; extra-args: --verify-feed require refuses then too, --verify-feed off skips the check. The scan also never reads more than a real feed's size. limbo.watch is now HTTPS-only and served from Cloudflare R2. Upgrade from 0.1.0a14 and earlier. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a14
Limbowatch 0.1.0a14 (alpha). Fixed: advisory fields typed by maintainers (version ranges, fixed versions, package names) could break or inject Markdown in issues, comments and job summaries; a range like >=4.1.0, <=4.1.13 || >=5.0.0, <5.1.1 showed only its first half. Every such field is now shown as code. install: python now installs exactly the dependency versions in uv.lock, checked against their hashes. The README documents what the scan reads, every host it contacts, and how to restrict it. Upgrade from 0.1.0a13 and earlier. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md
Limbowatch 0.1.0a13
Limbowatch 0.1.0a13 (alpha). Fixed: advisory ranges with one upper bound per release line, such as <= 2.12.6, <= 2.11.15, hid affected versions (here 2.12.6); they are now read one bound per line, and a version on a line the range does not name is reported as possibly affected. Findings in a pom.xml now point at the dependency line. Upgrade from 0.1.0a12 and earlier. Full notes: https://github.com/limbowatch/limbowatch/blob/main/CHANGELOG.md