finding
Findings for the configured analysis.
list
Search findings across the currently configured project, or the --project, or search across the entire team by using --all.
bevor finding list [OPTIONS]Arguments:
--pageintegerPage number to use for resource that supports pagination
--page-sizeintegerPage size to use for resource that supports pagination
--orderchoiceHow to order results when a resource supports pagination
--order-bychoiceWhat field to order results by when a resource supports pagination
--projecttextProject id to filter by.
--selfbooleanFilter by findings in analyses the caller owns.
--usertextFilter by user id (user who owns the analysis the finding is in)
--codetextCode Id to filter by.
--analysestextAnalysis ids to filter by (comma separated)
--typechoiceFinding type.
--levelchoiceFinding level.
--acknowledgedbooleanFilter by acknowledgement status.
--operationchoiceStaged draft operation.
--created-by-selfbooleanFilter by findings the caller is original creator of
--created-bytextFilter by original creator of a finding.
--allbooleanShow findings across all projects
--jsonbooleanJSON output
get
Get the finding details.
bevor finding get [OPTIONS]Arguments:
finding_idtextrequiredFinding ID.
--jsonbooleanJSON output
add
Stage a new finding to your currently configured analysis, or to the --version.
Provide input one of three ways:
--file: a YAML file with exactly one finding mapping.--interactive: prompts for each field.- Flags directly, as described below.
When passing flags, specify a location, which specifies the code node that the finding is associated with, using exactly one of:
--nodeand/or--location(a Bevor node id;--locationalone fans the finding out to every entrypoint that reaches it)--uriplus one full pair of--start-line/--end-line,--char-offset/--char-length, or--byte-offset/--byte-length--fqn
Metadata (--type, --level, --name, --explanation) is all or
nothing: provide all four to record a finding, or omit all four to mark the
location as analyzed with no finding. --recommendation, --reference,
and --source are always optional.
bevor finding add [OPTIONS]Arguments:
--versiontextVersion id to stage against (default: configured analysis head).
--filepathYAML file containing exactly one finding mapping.
--interactivebooleanForce interactive prompts.
--typetext--levelchoice--nametext--explanationtext--recommendationtext--referencetext--sourcetext--nodetext--locationtext--uritext--start-lineinteger--start-columninteger--end-lineinteger--end-columninteger--char-offsetinteger--char-lengthinteger--byte-offsetinteger--byte-lengthinteger--fqntextbulk
Import many findings at once to the configured analysis head, or --version if given
source is dispatched by type:
- a directory: every
.yaml/.ymlfile in it is parsed, each of which may itself contain multiple findings (----separated documents). - a
.yaml/.ymlfile: parsed the same way, as a single source. - a
.sariffile: converted from SARIF into Bevor findings.
bevor finding bulk [OPTIONS]Arguments:
sourcepathrequiredA .json file, .sarif file, .yaml/.yml file, or a directory of YAML files.
--versiontextVersion id to stage against (default: configured analysis head).
edit
Stage an edit to a finding (--file YAML or interactive matching current metadata).
bevor finding edit [OPTIONS]Arguments:
finding_idtextrequiredFinding id to edit.
--file, -fpathYAML with one mapping: type, level, name, explanation; optional recommendation / reference.
delete
Stage a finding deletion.
bevor finding delete [OPTIONS]Arguments:
finding_idtextrequiredFinding id to delete.
revert
Revert a staged finding change.
bevor finding revert [OPTIONS]Arguments:
finding_idtextrequiredFinding id to revert.
acknowledge
Toggle acknowledgement status for a finding.
bevor finding acknowledge [OPTIONS]Arguments:
finding_idtextrequiredFinding id to toggle validation for.