Files
git.stella-ops.org/docs/product-advisories/30-Nov-2025 - Comparative Evidence Patterns for Stella Ops.md
StellaOps Bot 18d87c64c5 feat: add PolicyPackSelectorComponent with tests and integration
- Implemented PolicyPackSelectorComponent for selecting policy packs.
- Added unit tests for component behavior, including API success and error handling.
- Introduced monaco-workers type declarations for editor workers.
- Created acceptance tests for guardrails with stubs for AT1–AT10.
- Established SCA Failure Catalogue Fixtures for regression testing.
- Developed plugin determinism harness with stubs for PL1–PL10.
- Added scripts for evidence upload and verification processes.
2025-12-05 21:24:34 +02:00

845 B

30-Nov-2025 · Comparative Evidence Patterns for Stella Ops

Why now: UX and data-model decisions need a grounded comparison of evidence/suppression patterns across major vendors.

Scope

  • Summarise how Snyk, GitHub, Aqua, Anchore/Grype, and Prisma Cloud handle evidence, suppression, audit/export.
  • Feed UX/data-model decisions for VEX, evidence views, and export policies.
  • Drives task 23 (EVIDENCE + suppression pattern sync) in sprint tracker.

Required artefacts (MVP)

  • This brief plus links to any UI or schema follow-ups once drafted.
  • Sprint tracker row 23 updated when evidence is logged.

Determinism & Offline

  • Keep examples deterministic; no live API calls in comparisons; cite cached docs/artefacts where needed.

Next actions

  • Add schema/UX notes to module docs when ready; log completion in Execution Log.