Saffron

ZokyoCode version: not recorded (see the report)

Zokyo reviewed saffron.finance (Saffron) on 11 Jan 2022: 8 findings, 0 critical; 4 marked fixed, 4 acknowledged.

No open critical findings
Open the reportOpen saffron.finance’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings14

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium000
Low043

Marked informaional or informational by the firm. Not counted as findings.

informaionalOrder of Layout, order of functions and naming conventionsAcknowledged

The report gives no description here.

informationalDebugger import and Hardhat's console.log is on audit commitsFixed

The report gives no description here.

informationalMisleading comment at line 22 of SaffronPoolV2Fixed

The report gives no description here.

informationalNot indexed address parameters in eventsFixed

The report gives no description here.

informationalReturn URI for unexciting tokenIdFixed

The report gives no description here.

informationalUnused local variable at SaffronConverter.solFixed

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 saffron.finance’s security record

saffron.finance
Audits8 audits by 5 firmsLast audit Mar 2026, by Pashov Audit Group.
Critical findingsNo open critical findingsAcross the 8 reports, 3 critical findings were reported. Each is marked fixed by the firm that reported it.
Open saffron.finance’s security record

Security firm

Zokyo

156 projects reviewed · 225 reports · latest May 2026

See Zokyo’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.

Tell us