-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
None
-
3
-
False
-
None
-
False
-
-
The 4.16 SAST scan created a bug which is quite extensive, for that reason we decided to deal with it as a story.
AC:
- Go though the list of identified vulnerabilities which are listed in the bug and decide which are valid issues and which are false positive
- Fix valid issues or update necessary deps
- Create a snyk config to avoid the SAST scanner from scanning dev files (tests, ...)
[CONSOLE-3918] Identify the 4.16 SAST scan issues
Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Stale issues rot after 30d of inactivity.
Mark the issue as fresh by removing the `lifecycle-rotten` label.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so. Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Samuel Padgett
added a comment - Issues go stale after 90d of inactivity.
Mark the issue as fresh by removing the `lifecycle-stale` label.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by adding the `lifecycle-frozen` label.
If this issue is safe to close now please do so.
Rotten issues close after 30d of inactivity.
You may reopen the issue by moving it back to TODO state and removing the `lifecycle-rotten` label. Exclude this issue from closing again by adding the `lifecycle-frozen` label.