2 commits

Author	SHA1	Message	Date
SHL0MS	d5fd74cac2	fix(ci): don't fail supply chain scan when PR comment can't be posted on fork PRs (#6681) ... The GITHUB_TOKEN for fork PRs is read-only — gh pr comment fails with 'Resource not accessible by integration'. This caused the supply chain scan to show a red X on every fork PR even when no findings were detected. The scan itself still runs and the 'Fail on critical findings' step still exits 1 on real issues. Only the comment posting is gracefully skipped for fork PRs. Closes #6679 Co-authored-by: SHL0MS <SHL0MS@users.noreply.github.com>	2026-04-13 13:58:59 -07:00
Teknium	ac5b8a478a	ci: add supply chain audit workflow for PR scanning (#2816) ... Scans every PR diff for patterns associated with supply chain attacks: CRITICAL (blocks merge): - .pth files (auto-execute on Python startup — litellm attack vector) - base64 decode + exec/eval combo (obfuscated payload execution) - subprocess with encoded/obfuscated commands WARNING (comment only, no block): - base64 encode/decode alone (legitimate uses: images, JWT, etc.) - exec/eval alone - Outbound POST/PUT requests - setup.py/sitecustomize.py/usercustomize.py changes - marshal.loads/pickle.loads/compile() Posts a detailed comment on the PR with matched lines and context. Excludes lockfiles (uv.lock, package-lock.json) from scanning. Motivated by the litellm 1.82.7/1.82.8 credential stealer attack (BerriAI/litellm#24512).	2026-03-24 08:56:04 -07:00