Update an existing finding in a repository.
Access control rules
- The requester must have access to the repository.
- Reviewers can update findings they and their team made.
- Clients, judges, triagers and admins can update any finding.
Note that what user can update what field (and to what value) depends on the user’s role, repository kind and status.
Documentation Index
Fetch the complete documentation index at: https://docs.cantina.xyz/llms.txt
Use this file to discover all available pages before exploring further.
Path Parameters
Reference to a finding, either a finding id or finding number.
Body
Status of a [Finding].
Note that the in_review status is only applicable within bounties.
new, in_review, disputed, rejected, spam, duplicate, confirmed, acknowledged, fixed, withdrawn When this field is set it overwrites the existing value, i.e. all URLs must be provided.
Only valid if the status is set to duplicate.
Severity of a [Finding].
critical, high, medium, low, informational, gas_optimization Likelihood of a [Finding].
high, medium, low Impact of a [Finding].
high, medium, low Can only be set by judges, triagers and admins.
high, medium, low Can only be set by admins.
Delete or add a related file to a finding.
- Option 1
- Option 2
Delete or add labels to a finding.
- Option 1
- Option 2
Delete or add asset groups to a finding.
- Option 1
- Option 2
- Option 3
Assign the finding to a user by id.
Update the locked state of the finding.
Note field for additional finding information.
Response
Finding updated