Azuro security review

Pashov Audit Group27 Mar 2023Code version: not recorded (see the report)

Pashov Audit Group reviewed Azuro (Azuro security review) on 27 Mar 2023: 15 findings, 0 critical; all marked fixed.

No open critical findings

Open the report Open Azuro’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings15

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

Severity	Open	Acknowledged	Fixed
Critical	0	0	0
High	0	0	0
Medium	0	0	5
Low	0	0	10

Marked QA by the firm. Not counted as findings.

QAMethod inherited from interface is missing the override keywordFixed

The report gives no description here.

QAOpen TODO in codeFixed

The report gives no description here.

QARedundant codeFixed

The report gives no description here.

QASmall issues in initializer methodsFixed

The report gives no description here.

QATypos in NatSpecFixed

The report gives no description here.

QAUnused importsFixed

The report gives no description here.

QAUse a safe pragma statementFixed

The report gives no description here.

QAUse braces around operators with uncertain precedenceFixed

The report gives no description here.

QAWrong importFixed

The report gives no description here.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Part of Azuro’s security record

Azuro

Audits3 audits by 2 firmsLast audit Feb 2024, by Pashov Audit Group.

Critical findingsNo open critical findingsAcross the 3 reports, 2 critical findings were reported. Each is marked fixed by the firm that reported it.

Open Azuro’s security record

Security firm

Pashov Audit Group

30 projects reviewed · 53 reports · latest Jul 2026

See Pashov Audit Group’s audits

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.