Vyper audit reports

Vyper has 1 public audit report from ChainSecurity; dated 13 Jun 2023; no critical findings reported.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm27

Statuses are the security firms’ own

27 findings are still open or acknowledged in the firms’ reports: 3 medium, 24 low (all open).

Medium
3
Low
24
  • Medium Open

    Incorrect Order of Evaluation of Arguments of Builtin Function

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Medium Open

    Make_setter Is Incorrect for Complex Types When the RHS References the LHS With a Function Call

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Medium Open

    Metadata Journal Can Rollback Incorrectly

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    Assertion Could Be More Precise in parse_Binop

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    Assertions Are Not Constant

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    Calls to State-Modifying Functions in Range Expressions Are Not Caught by the Type-Checker

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    Default Arguments Are Treated as Keyword Arguments

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    Epsilon Is Not Documented

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    IfExp Cannot Be Used in a Subscript

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

  • Low Open

    IfExp Fails at Codegen When Used With Self or Environment Variables

    Vyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023 · Report ↗

All 27 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Vyper Compiler 0.4.2 Pull RequestsSecurity firm: ChainSecurityDate: Scope: Not recorded; see the reportNone openFindings: 3 medium · 24 low
27 open
chainsecurity.com ↗

Findings27

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium300
Low2400
MediumIncorrect Order of Evaluation of Arguments of Builtin FunctionVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
MediumMake_setter Is Incorrect for Complex Types When the RHS References the LHS With a Function CallVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
MediumMetadata Journal Can Rollback IncorrectlyVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowAssertion Could Be More Precise in parse_BinopVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowAssertions Are Not ConstantVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowCalls to State-Modifying Functions in Range Expressions Are Not Caught by the Type-CheckerVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowDefault Arguments Are Treated as Keyword ArgumentsVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowEpsilon Is Not DocumentedVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowIfExp Cannot Be Used in a SubscriptVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowIfExp Fails at Codegen When Used With Self or Environment VariablesVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
Show 10 more
LowIfExp Not Annotated When Used as Iterable for a LoopVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowImplements Statement Does Not Enforce the Same Indexation of EventsVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowImported Contracts Are Not Fully Semantically ValidatedVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
Lowin and Not in Cannot Be Used With DynArray of EnumsVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowIncorrect Typing of Builtins Whose Return Type Depends on Some of Its Argument's TypesVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowIncorrect Typing of Loop Iterable When It Is a List LiteralVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowIncorrect Typing of Raw_Call When Max_Outsize=0 in KwargsVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowMultiple Evaluations of DST Lead to Non-Unique Symbol Errors When Copying Bytes Arrays or DynArraysVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowNesting a Pop in Append Results in Incorrect BehaviorVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowNo Sanity Check on Storage Layout FilesVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
Show 7 more
LowOverriding Storage Layout Fails With ImmutablesVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowPR 3134 Has Been RevertedVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowRedundant and Incomplete Function Selector Collision ChecksVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowReferences to Public Constant and Immutables With Self Missed by the TypecheckerVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowSemantic Analysis of the Imported Contract Is Done With the Current Contract's NamespaceVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowStateAccessViolation When "Self" Is Used as a Struct Field NameVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report
LowTypecheckFailure When Using Address and Self Members as Struct Field NameVyper Compiler 0.4.2 Pull Requests · ChainSecurity · 13 Jun 2023Open

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Vyper: questions

Is Vyper audited?

Trustblock holds 1 public audit report for Vyper, dated 13 Jun 2023. The latest is by ChainSecurity (“Vyper Compiler 0.4.2 Pull Requests”).

Who audited Vyper?

ChainSecurity wrote the report Trustblock holds for Vyper.

Are there open findings in Vyper’s audits?

27 findings are still open or acknowledged in the firms’ reports: 3 medium, 24 low (all open). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="vyper"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.

Tell us