List view
A security engineer, when viewing their organization's projects, should be able to take a "deep dive" into their findings and understand, more holistically, whether a specific finding is relevant. They might have specific, contextual understanding of the application as it relates to their company and want to either "upvote" or "downvote" vulnerabilities from being displayed in the UI for engineers. This view should arm the security information with simple, but meaningful information about where the code is being called.
No due date•0/1 issues closedDeveloping new features for LunaTrace should easily be deployed and deployed in a way that is reliable and fool proof. Additionally, debugging the application locally and in production should be effortless and understanding why a task is failing should be trivial.
No due date•0/1 issues closed- No due date•2/2 issues closed
This milestone also contains: - (FE24) Affected Transient Dependency not Exploitable Check
No due date- No due date
- No due date
- No due date
This also contains as nested milestones: - (FE17) Dependencies not Used in Code Check - (FE16) Affected Code Library is Vulnerable but not Exploitable Check
No due date•2/4 issues closed- No due date
- No due date
- No due date
- No due date
- No due date
- No due date
- No due date
- No due date•1/1 issues closed
- No due date
- No due date•7/8 issues closed
- No due date•1/2 issues closed
- No due date•7/7 issues closed