Skip to content

security: WS49/WS50 supply-chain hardening + docs#2

Merged
brokenbot merged 1 commit into
mainfrom
security/ws49-ws50-hardening
Jun 7, 2026
Merged

security: WS49/WS50 supply-chain hardening + docs#2
brokenbot merged 1 commit into
mainfrom
security/ws49-ws50-hardening

Conversation

@brokenbot

Copy link
Copy Markdown
Collaborator

Summary

Hardens the Python adapter SDK. Library — no binary, so multi-arch N/A. The repo had no CI workflow; this adds one.

  • WS49: osv-scanner.toml; new ci.yml with a blocking osv-scan (pinned google/osv-scanner-action v2.3.8) that scans uv.lock explicitly (the directory walk does not auto-detect uv.lock — it returns "No package sources found"), plus build/test (uv) and a non-blocking uv pip list --outdated report. make vuln-scan. Tree clean (19 packages, 0 advisories).
  • WS50: docs/dependency-policy.md (no update bot; uv tooling).
  • Docs: README security section, SECURITY.md, all-checks gate.

Test plan

  • osv-scanner clean against uv.lock; YAML valid
  • CI green on branch (uv sync + make test + osv-scan)

Python library (no published binary). Port the supply-chain hardening:
- WS49: osv-scanner.toml; NEW ci.yml with blocking osv-scan (pinned action,
  scans uv.lock explicitly — the dir walk does not auto-detect uv.lock);
  make vuln-scan. Tree clean (19 packages, 0 advisories).
- WS50: docs/dependency-policy.md (no update bot; uv pip list --outdated);
  non-blocking deps-report CI job.
- Docs: README security section; SECURITY.md (library variant); all-checks gate.
@brokenbot brokenbot merged commit 97bad9a into main Jun 7, 2026
4 checks passed
@brokenbot brokenbot deleted the security/ws49-ws50-hardening branch June 7, 2026 01:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant