Astroport Governance audit

Oak SecurityCode version: not recorded (see the report)

Oak Security reviewed Astroport (Astroport Governance audit) on 15 Mar 2022: 7 findings, 1 critical; 6 marked fixed, 1 acknowledged.

1 critical finding, fixed
Open the reportOpen Astroport’s security record

Report hosted on GitHub.

Trustblock does not review code.

Findings7

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

SeverityOpenAcknowledgedFixed
Critical001
High002
Medium000
Low013
CriticalClaiming allocation will cause proposed receiver’s original allocation to be overwritten, leaving funds inaccessible in the contractFixed

The report gives no description here.

HighLeftover amount after providing liquidity is not refundedFixed

The report gives no description here.

HighOriginal receivers that transferred allocation will not be able to receive new allocationsFixed

The report gives no description here.

LowExtra funds sent to AstroZap contract are lostFixed

The report gives no description here.

LowMisconfigured schedule duration could cause division by zero error, leaving funds inaccessibleFixed

The report gives no description here.

LowUnlockedTokens query message does not include cliff period during calculationFixed

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 Astroport’s security record

Astroport
Audits12 audits by 1 firmLast audit Mar 2025, by Oak Security.
Critical findingsNo open critical findingsAcross the 12 reports, 8 critical findings were reported. Each is marked fixed by the firm that reported it.
Open Astroport’s security record

Security firm

Oak Security

33 projects reviewed · 60 reports · latest May 2026

See Oak Security’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