Foodriver

QuillAudits31 May 2024Code version: not recorded (see the report)

Audit · firm’s term: audit report

QuillAudits reviewed Foodriver on 31 May 2024: 11 findings, 0 critical; 8 marked fixed, 3 open.

No open critical findings

Open the report Open Foodriver’s security record

Report hosted on quillaudits.com.

Trustblock does not review code.

Findings11

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

Severity	Open	Fixed
Critical	0	0
High	0	2
Medium	1	2
Low	2	4

MediumInaccurate token pricing in FooDriverToken could allow users get more tokens at less cost to themOpen

The FooDriverToken contract allows users to purchase tokens in the private sale and the public sale via supportedTokens added by the registry. The issue here lies with the rates which are manually added - if there happens to be a change in the price of the tokens supported via a depeg or improper rate adjustments before the user with DEFAULT_ADMIN_ROLE gets to update it, tokens will be improperly priced until that update occurs.

LowCode reuseOpen

A number of functions and modifiers are reused across almost all contracts. The continued repetition could signify the need for a helper contract that can be inherited where necessary. Having modular code enhances code readability and reduces complexity when handling and extending multiple contracts.

LowLow test coverageOpen

Unit tests are used to ensure that the code functions as expected by passing in varying user input and setting up various parameters to test the boundaries of the protocol. There are no unit test cases associated with the codebase provided, hereby increasing the probability of bugs being present and reducing quality assurance.