MILO Project has 1 public audit report from CertiK; dated 31 Jan 2023; no critical findings reported.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
1 finding is still open or acknowledged in the firms’ reports: 1 high.
Centralization Risks in milo.sol
Milo · CertiK · 31 Jan 2023 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| Milo | Security firm: CertiK | Date: | Scope: Files listed | None open | Findings: 2 high · 10 low 11 fixed · 1 open | skynet.certik.com ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 1 | 0 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 10 |
In the contract `Milo` the role `owner` has authority over the functions shown in the diagram below. Any compromise to the `owner` account may allow the hacker to take advantage of this authority and can arbitrarily mint/burn the `Milo` tokens. 
Open the reportThe reports name a repository or files. Open a report to see its scope.
Trustblock holds 1 public audit report for MILO Project, dated 31 Jan 2023. The latest is by CertiK (“Milo”).
CertiK wrote the report Trustblock holds for MILO Project.
1 finding is still open or acknowledged in the firms’ reports: 1 high. No critical finding is reported. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="milo-1"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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