[fas89]

pip-audit (the Security Scan job) has failed on every new run since 2026-10-29: filelock published advisories in waves — 13 since 2026-10-26, 10 of them today — all fixed only in filelock 4.x (4.0.9 / 4.2.1). That fix cannot resolve here: litellm, a base dependency, still declares filelock<4.0 in its latest release (1.106.6, checked against the PyPI JSON API); upstream tracker BerriAI/litellm#48394.

Ignoring them by ID (the first version of this PR, and the three IDs ignored on 2026-10-26) chased a moving target. Founder decision 2026-10-29: allow only what the cap makes unfixable.

What changed

The step runs pip-audit --desc --format json and a small inline filter:

• a filelock 3.x advisory whose only fix is >= 4.0 is printed as a ::warning:: with the litellm note;
• everything else fails the gate: any other package, a filelock advisory fixable inside 3.x or with no fix listed, and a pip-audit run that errors or writes no report.

The comment records what the filelock advisories touch: ReadWriteLock and StrictSoftFileLock are used by nothing in the closure; the plain FileLock (pip/cachecontrol, huggingface_hub, litellm, safety, mypy) and SoftFileLock (huggingface_hub's fallback) are, with lock files in the running user's own caches, and all need a second local user (AV:L). fluid_build never imports filelock. Remove the allowance when litellm lifts the cap (the re-check command is in the comment).

Validation

• actionlint: clean.
• The filter, run on synthetic pip-audit reports: only-4.x filelock → exit 0 with warnings; plus another vulnerable package → exit 1; a filelock fix inside 3.x → exit 1; no fix listed → exit 1; clean → exit 0; no report → exit 1; pip-audit exit 2 → exit 1.
• On a real pip-audit -r <filelock==3.32.7> --format json report: 13 advisories, all allowed, exit 0. The JSON keys the filter reads (dependencies[].name/version/vulns[].id/fix_versions) are pip-audit's.

Documentation

• Docs PR linked
• No docs needed (CI configuration)
• Docs TODO