Skip to content

[codex]: there are no vulnabilirity found in this contracts #1620

Open
@skimaharvey

Description

@skimaharvey

Describe the issue:

Screenshot 2023-01-21 at 14 35 22

I guess not that much of a big deal but probably could filter out this type of "finding"?

Code example to reproduce the issue:

Coming from a private repo

Version:

0.9.2

Relevant log output:

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    bug-candidateBugs reports that are not yet confirmed

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions