HealthFi Token
Audit · firm’s term: audit report
Cyberscope reviewed HealthFi Token on 23 May 2022: 6 findings, 0 critical; none marked fixed.
No open critical findings
Open the reportOpen HealthFi Token’s security record
Report stored on IPFS. Content hash bafkreicaxzqigajptjqaesfifwxacsttu5ow56aphzbst4ddxdrnwc2az4
Trustblock does not review code.
Findings6
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 | 6 | 0 | 0 |
LowL01 - Public Function could be Declared ExternalOpen
The report gives no description here.
LowL02 - State Variables could be Declared ConstantOpen
The report gives no description here.
LowL04 - Conformance to Solidity Naming ConventionsOpen
The report gives no description here.
LowL09 - Dead Code EliminationOpen
The report gives no description here.
LowL14 - Uninitialized Variables in Local ScopeOpen
The report gives no description here.
LowOCTD - Owner Contract Tokens DrainOpen
The report gives no description here.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0x0effec9798e84b70c9136f9e086fdd5baad4a2d5 | Chain: BNB Chain | Source code: Verified source |
Part of HealthFi Token’s security record
HealthFi Token
Audits3 audits by 1 firmLast audit Jul 2022, by Cyberscope.
Critical findings2 open critical findingsReported in “Fitness Token” by Cyberscope, Jul 2022. Not marked fixed in that report.
Open HealthFi Token’s security recordSecurity firm
Cyberscope1,783 projects reviewed · 2,056 reports · latest Oct 2026
See Cyberscope’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