Kepler Digitals / Token
Hacken reviewed Kepler Digitals (Kepler Digitals / Token) on 31 Oct 2024: 8 findings, 0 critical; 6 marked fixed, 2 open.
Report hosted on hacken.io.
Trustblock does not review code.
Findings8
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 | 2 | 0 | 6 |
LowAdmin can be blacklistedFixed
The report gives no description here.
LowFunctions not used internally can be marked as externalFixed
The report gives no description here.
LowLack of fine-grained access controlFixed
The report gives no description here.
LowLack of named parameters in mappingFixed
The report gives no description here.
LowNon-Compliance with naming conventions for contract and file namesFixed
The report gives no description here.
LowUnauthorized Token Burn via burnFrom FunctionFixed
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.
Repository and files the report names (1)
- KeplerDigitals___Avia-Token/contracts/AVIA.sol
Part of Kepler Digitals’s security record
Kepler DigitalsSecurity firm
Hacken343 projects reviewed · 476 reports · latest Sep 2026
See Hacken’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