nessi/NexaPG
1
0
Fork 0
Code Issues 16 Pull Requests Actions Packages Projects Releases 14 Activity

[NX-202] Enforce Python dependency security gate (pip audit) #12

New Issue
Closed
opened 2026-02-13 13:17:10 +00:00 by nessi · 1 comment
nessi commented 2026-02-13 13:17:10 +00:00
Owner
Copy Link

Goal

Prevent shipping known vulnerable Python dependencies.

Scope

  • Add dependency scan (pip audit) in CI.
  • Fail on high/critical unresolved issues.

Acceptance Criteria

  • CI blocks vulnerable dependency updates.
  • Security exception flow is documented.
## Goal Prevent shipping known vulnerable Python dependencies. ## Scope - Add dependency scan (`pip audit`) in CI. - Fail on high/critical unresolved issues. ## Acceptance Criteria - CI blocks vulnerable dependency updates. - Security exception flow is documented.
nessi added this to the v1.0 - Stability, Reliability & Security (P0) milestone 2026-02-13 13:17:10 +00:00
nessi added the P0 label 2026-02-13 13:17:10 +00:00
nessi commented 2026-02-15 10:27:53 +00:00
Author
Owner
Copy Link

NX-202 Completed

Implemented Python dependency vulnerability enforcement in CI with a documented, auditable exception flow.

Delivered Scope

  • Added dedicated CI workflow for dependency scanning:
    • .github/workflows/python-dependency-security.yml
    • Runs pip-audit on backend dependencies.
  • Added policy gate script:
    • backend/scripts/pip_audit_gate.py
    • Blocks unresolved HIGH / CRITICAL findings.
    • Treats missing severity metadata conservatively as HIGH.
  • Added explicit allowlist mechanism:
    • ops/security/pip-audit-allowlist.json
    • Supports temporary exceptions with required metadata and expiry.
  • Added documentation for exception handling:
    • docs/security/dependency-exceptions.md
  • Added release-time dependency gate:
    • docker-release.yml now runs pip-audit + policy gate before image build/push.

Acceptance Criteria Mapping

  • CI blocks vulnerable dependency updates
    Met: unresolved high/critical findings fail the dependency security workflow and release pipeline.

  • Security exception flow is documented
    Met: exception process, required fields, expiry rules, and auditability are documented in docs/security/dependency-exceptions.md.

Notes

  • No database migration required.
  • This closes NX-202 from implementation perspective.
## NX-202 Completed Implemented Python dependency vulnerability enforcement in CI with a documented, auditable exception flow. ### Delivered Scope - Added dedicated CI workflow for dependency scanning: - `.github/workflows/python-dependency-security.yml` - Runs `pip-audit` on backend dependencies. - Added policy gate script: - `backend/scripts/pip_audit_gate.py` - Blocks unresolved `HIGH` / `CRITICAL` findings. - Treats missing severity metadata conservatively as `HIGH`. - Added explicit allowlist mechanism: - `ops/security/pip-audit-allowlist.json` - Supports temporary exceptions with required metadata and expiry. - Added documentation for exception handling: - `docs/security/dependency-exceptions.md` - Added release-time dependency gate: - `docker-release.yml` now runs `pip-audit` + policy gate before image build/push. ### Acceptance Criteria Mapping - **CI blocks vulnerable dependency updates** Met: unresolved high/critical findings fail the dependency security workflow and release pipeline. - **Security exception flow is documented** Met: exception process, required fields, expiry rules, and auditability are documented in `docs/security/dependency-exceptions.md`. ### Notes - No database migration required. - This closes NX-202 from implementation perspective.
nessi closed this issue 2026-02-15 10:27:55 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P0
High priority
 P1
Medium priority
 P2
Low priority
No Label P0
Milestone
No items
No Milestone v1.0 - Stability, Reliability & Security (P0)
Projects
Clear projects
No project
Assignees
Clear assignees
nessi
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: nessi/NexaPG#12
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?