-
Notifications
You must be signed in to change notification settings - Fork 3
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.
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
QA Report #174
Comments
141345 marked the issue as sufficient quality report |
QA JudgmentThe Warden's QA report has been graded B based on a score of 20 combined with a manual review per the relevant QA guideline document located here. The Warden's submission's score was assessed based on the following accepted findings: Low-Risk |
alex-ppg marked the issue as grade-b |
Hey, L-06 is a duplicate of 1148, and I believe its severity should not be 'L' but marked as 'M' and marked as dupe. The same should be done with L-02, as it also points to the main root cause and is explained good enough, although shortly. The only issue is that I have misjudged the severity of those findings, I didn't submit them as medium in order to not spam the contest with inflated findings. Generally it is recommended that hard to qualify finding should be submitted as LOWs and if it's a MED the judge will raise it to it's appropriate severity. |
Hey @0x3b33, thanks for contributing! Submission #1148 ended up being nullified in the PJQA process. Concerning #1275, I do not deem this submission to be of sufficient quality to be eligible for a portion of its rewards. #1275 and its duplicates have a detailed PoC, elaborate on what the impact is, how it should be corrected, etc. In the interest of fairness, I cannot provide this QA submission a reward as its comparative quality is very low and it would incentivize giant QA reports to be submitted that detail all issues and leave the burden of upgrading to the judges which is unfair from a contest's perspective. |
See the markdown file with the details of this report here.
The text was updated successfully, but these errors were encountered: