Aperture audit
Audit · firm’s term: security audit
Oak Security reviewed Aperture (Aperture audit) on 8 Mar 2022: 4 findings, 0 critical; 2 marked fixed, 2 acknowledged.
No open critical findings
Open the reportOpen Aperture’s security record
Report hosted on GitHub.
Trustblock does not review code.
Findings4
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 | 0 |
| Low | 0 | 2 | 2 |
Marked Informational by the firm. Not counted as findings.
InformationalCertain cross-chain and Terra transfers are overly permissiveAcknowledged
The report gives no description here.
InformationalDelta neutral position should implement a “migrate only if newer” patternAcknowledged
The report gives no description here.
Informationalmigrate_position_contracts allows anyone to perform migrationsAcknowledged
The report gives no description here.
InformationalUse of the term “info” may impact readabilityFixed
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 Aperture’s security record
ApertureAudits1 audit by 1 firmLast audit Mar 2022, by Oak Security.
Critical findingsNo open critical findingsIn 1 report.
Open Aperture’s security recordSecurity firm
Oak Security33 projects reviewed · 60 reports · latest May 2026
See Oak Security’s auditsSomething 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