Pudge Inu
Cyberscope reviewed Pudge Inu on 22 Apr 2022: 4 findings, 0 critical; none marked fixed.
No open critical findings
Open the reportOpen Pudge Inu’s security record
Report stored on IPFS. Content hash bafkreic4p5vbgifybyr3ukbhkls6jbqd4s3umzlgfb7idvk4go4lpnfj74
Trustblock does not review code.
Findings4
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 | 4 | 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.
LowL05 - Unused State VariableOpen
The report gives no description here.
Contracts in scope1
| Address | Chain | Source code |
|---|---|---|
| 0xa7094b0488b8f3ed9e17e97a77e9cdb12b0b61f3 | Chain: BNB Chain | Source code: Verified source |
Part of Pudge Inu’s security record
Pudge Inu
Audits1 audit by 1 firmLast audit Apr 2022, by Cyberscope.
Critical findingsNo open critical findingsIn 1 report.
Open Pudge Inu’s security recordSecurity firm
Cyberscope1,777 projects reviewed · 2,050 reports · latest Sep 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