Skip to content

feat: 006 finding occurrence and lineage lifecycle 구현 #271

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
goodtu02 merged 4 commits into from
Jul 30, 2026
Merged

feat: 006 finding occurrence and lineage lifecycle 구현 #271

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
fd83954
feat: implement finding lineage lifecycle
goodtu02 Jul 30, 2026
f24729e
fix: address finding lineage review feedback
goodtu02 Jul 30, 2026
c947aa7
fix: harden finding lineage review boundaries
goodtu02 Jul 30, 2026
ace1d69
fix: complete finding lineage review hardening
goodtu02 Jul 30, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 3 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -68,8 +68,9 @@ Start from its
| Legacy MVP | Historical baseline in [`001-aegisai-mvp-foundation`](./specs/001-aegisai-mvp-foundation/) and [`spec 2.2.md`](./spec%202.2.md) |

The 006 package makes the SAST runtime implementation-ready before provider execution:
fixed-commit isolated scans, hostile-input validation, deterministic normalization and
finding identity, fail-closed coverage, reduced evidence, and measurable rule/runtime gates.
fixed-commit isolated scans, hostile-input validation, deterministic normalization,
repository-scoped finding lineage with target-scoped lifecycle history, fail-closed coverage,
reduced evidence, and measurable rule/runtime gates.
The 005 baseline still governs the later live Kubernetes and provider-specific microVM
rollout; production credentials and live provider execution remain deferred.

Expand Down
Loading
Loading