Skip to content

ci: scan the Python CI locks with osv-scanner and drop the stale jackson waiver - #506

Merged
kingchenc merged 1 commit into
mainfrom
ci/osv-requirements
Nov 2, 2026
Merged

kingchenc merged 1 commit into
mainfrom
ci/osv-requirements

Conversation

@kingchenc

Copy link
Copy Markdown
Collaborator

The blind spot

OSV-Scanner discovers lockfiles by filename. None of bench.txt, ci-dev-py3.txt and ci-dev-py39.txt matches a pattern it recognises, so --recursive walked past all of .github/requirements/. The scan listed every Cargo, npm, Go, Maven and NuGet manifest and no Python lock. Renaming the files to requirements-*.txt makes them visible, so it is the filename and not the hidden .github directory.

The files keep their names (Dependabot, scripts/update-lockfiles.sh and the family use them) and the format is stated explicitly instead:

--lockfile=requirements.txt:.github/requirements/bench.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt

wickra-exchange did the same in wickra-lib/wickra-exchange#167 and recorded there that wickra had the same gap.

What surfaces: only GHSA-6w46-j5rx-g56g (pytest 8.4.2 in the 3.9 lock). osv-scanner.toml already carries a reasoned waiver for it, and until now that waiver applied to nothing. osv-scanner reported it as an unused ignore. Now it is load-bearing.

The jackson waiver was wrong, and is not needed

GHSA-72hv-8253-57qq was waived in three places (the root config and one next to each Maven manifest). The reasoning was that only jackson 2.x is present and the advisory covers 3.x. That stopped being true: the advisory now also covers com.fasterxml.jackson.core:jackson-core from 2.15.0, fixed in 2.18.6 and 2.21.1.

It is also not needed:

The one jackson left is jackson-databind 2.16.1 inside central-publishing-maven-plugin 0.12.0, which is the newest release. It runs in Maven on the release runner and is not a dependency of anything published. No scanner reads build-plugin trees, so a waiver for it waives nothing.

All three entries are removed. The two configs next to the Maven manifests contained nothing else and are deleted.

Smaller corrections

  • osv-scanner.toml header: it said the file mirrors the deny.toml ignore list, which is empty, and named Scorecard as its only reader. It now names the ci.yml step that passes it with --config.
  • SECURITY.md VEX section: it named only deny.toml as the record; osv-scanner.toml is the record for every other ecosystem.
  • .github/dependabot.yml:
    • The pip section said osv-scanner covers every ecosystem, which was not true for these files until now; that is now stated.
    • The Maven comment no longer mentions the examples' jackson.
  • ci.yml: the semver job's header comment had ended up between the cargo-deny and osv-scanner steps of the supply-chain job. It is back above semver:. YAML ignores comments, so nothing ran differently.

Verified

On a clean export of this branch, the step's exact scan-args:

Scanned .github/requirements/bench.txt file and found 14 packages
Scanned .github/requirements/ci-dev-py3.txt file and found 10 packages
Scanned .github/requirements/ci-dev-py39.txt file and found 14 packages
GHSA-6w46-j5rx-g56g and 2 aliases have been filtered out because: pytest is a CI-only test dependency, ...
No issues found

There are no unused ignores and the exit code is 0. actionlint is clean.

@codecov

codecov Bot commented Nov 2, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

This was referenced Nov 2, 2026
kingchenc added a commit to wickra-lib/wickra-gym that referenced this pull request Nov 2, 2026
#110)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt`, `ci-gymnasium.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
--lockfile=requirements.txt:.github/requirements/ci-gymnasium.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-genome that referenced this pull request Nov 2, 2026
#115)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-feature-store that referenced this pull request Nov 2, 2026
#116)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## --config is now explicit

The step ran without `--config`. Without it, osv-scanner looks for a config next to each lockfile, and none sits in `.github/requirements/`. Checked with `pytest==8.4.2` in `.github/requirements/` and a waiver for `GHSA-6w46-j5rx-g56g` in the root `osv-scanner.toml`: without `--config` the advisory is reported, with it it is filtered. The root config is the only `osv-scanner.toml` in this repository, so passing it explicitly changes nothing for the files the step already scanned.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-proof that referenced this pull request Nov 2, 2026
#139)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-darwin that referenced this pull request Nov 2, 2026
#113)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-copilot that referenced this pull request Nov 2, 2026
#168)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
@kingchenc
kingchenc merged commit 8dbce41 into main Nov 2, 2026
116 of 118 checks passed
@kingchenc
kingchenc deleted the ci/osv-requirements branch November 2, 2026 20:30
kingchenc added a commit to wickra-lib/wickra-screener that referenced this pull request Nov 2, 2026
#235)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## --config is now explicit

The step ran without `--config`. Without it, osv-scanner looks for a config next to each lockfile, and none sits in `.github/requirements/`. Checked with `pytest==8.4.2` in `.github/requirements/` and a waiver for `GHSA-6w46-j5rx-g56g` in the root `osv-scanner.toml`: without `--config` the advisory is reported, with it it is filtered. The root config is the only `osv-scanner.toml` in this repository, so passing it explicitly changes nothing for the files the step already scanned.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-backtest that referenced this pull request Nov 2, 2026
#180)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `bench.txt`, `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/bench.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-radar that referenced this pull request Nov 2, 2026
#162)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-compile that referenced this pull request Nov 2, 2026
#97)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-verify that referenced this pull request Nov 2, 2026
#141)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-shazam that referenced this pull request Nov 2, 2026
#166)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-zk that referenced this pull request Nov 2, 2026
#113)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-strategy-ci that referenced this pull request Nov 2, 2026
#110)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-xray that referenced this pull request Nov 2, 2026
#201)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## --config is now explicit

The step ran without `--config`. Without it, osv-scanner looks for a config next to each lockfile, and none sits in `.github/requirements/`. Checked with `pytest==8.4.2` in `.github/requirements/` and a waiver for `GHSA-6w46-j5rx-g56g` in the root `osv-scanner.toml`: without `--config` the advisory is reported, with it it is filtered. The root config is the only `osv-scanner.toml` in this repository, so passing it explicitly changes nothing for the files the step already scanned.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-timemachine that referenced this pull request Nov 2, 2026
#115)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-benchmark that referenced this pull request Nov 2, 2026
#106)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt`, `manifest.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
--lockfile=requirements.txt:.github/requirements/manifest.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-terminal that referenced this pull request Nov 2, 2026
#177)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `bench.txt`, `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/bench.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-impact that referenced this pull request Nov 2, 2026
#122)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
kingchenc added a commit to wickra-lib/wickra-synth that referenced this pull request Nov 2, 2026
#108)

## The blind spot

OSV-Scanner discovers lockfiles **by filename**. None of `ci-dev-py3.txt`, `ci-dev-py39.txt` matches a pattern it recognises, so `--recursive` walked past every hash-locked file in `.github/requirements/`, and the Python CI dependencies were never scanned. A file renamed to `requirements-*.txt` in the same directory is picked up, so it is the filename and not the hidden `.github` directory.

The files keep their names, which Dependabot, the lockfile refresh and the family use, and the format is stated explicitly instead:

```
--lockfile=requirements.txt:.github/requirements/ci-dev-py3.txt
--lockfile=requirements.txt:.github/requirements/ci-dev-py39.txt
```

wickra-lib/wickra-exchange#167 made the same change. wickra-lib/wickra#506 does it for `wickra`. The step's comment says a new file there needs a line here.

## Verified

The osv-scanner command was taken from the parsed workflow and run on a clean export of this branch:

- every file above is scanned;
- no finding (`No issues found`), exit code 0;
- no unused ignores;
- actionlint is clean.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant