Security Audit Report
</> APIOasisV40x9067462A6B…A8dc7ba8
37out of 100
2 blocking issues
At least one finding describes a plausible path to loss of funds or control. Read those findings before interacting with this contract.
- Findings
- 185
- Engines
- aderyn, slither
- Scanned
- Source
- Published
Findings by severity
Critical
0
High
2
Medium
9
Low
47
Informational
126
Gas
0
Findings (185)
2 checks · 2 instances
A plausible path to loss of funds or control. Treat as blocking.OasisV4 (project/contracts/oasisV4.sol#97-1002) contract sets array length with a user-controlled value: - ref_balances.push(_newRefBalances[i]) (project/contracts/oasisV4.sol#491)
The condition has been determined to be either always true or always false due to the integer range in which we're operating. [oasisV4.sol:459; oasisV4.sol:464]
5 checks · 9 instances
Can go wrong under specific conditions worth understanding first.19 checks · 47 instances
Worth knowing about. Rarely a reason on its own not to interact.1 check · 1 instance
Costs more gas than it needs to. Not a safety issue.5 checks · 126 instances
Style and convention. No effect on what the contract does.Scope and limitations
This is automated static analysis, run by aderyn and slither against this contract’s published source. It is not a manual audit and nobody has reviewed these results by hand.
- It finds known patterns. A novel bug, or one that depends on how this contract is used alongside another, is exactly what it does not find.
- It cannot judge intent. A contract that lets its owner mint without limit is working as written; whether that is acceptable is not a question a scanner answers.
- It says nothing about the people behind the contract, the liquidity, or whether the deployer still holds the keys.
- A high score means the analysers had few complaints. It is not a guarantee, an endorsement, or advice to interact.
Read the source yourself where it matters. This contract’s source is published.