C-Charge
SolidProof reviewed C+Charge (C-Charge) on 12 Dec 2022: 1 finding, 0 critical; it is not marked fixed.
No open critical findings
Open the reportOpen C+Charge’s security record
Report stored on IPFS. Content hash QmSihiy8MHtVUJJdqFk9eA1zjMUZvJaX7tqMuxzDUzLaP2
Statuses are the security firm’s own, from this report. Trustblock does not review code.
Findings1
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 | 1 | 0 | 0 |
Low#1: NatSpec documentation missingNot fixed
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)
- https://github.com/C-ChargeDev/ERC20/contracts/Token.sol at commit 1ac1e8f0d2680d93ed68db19d30fc743cdd98504
Part of C+Charge’s security record
C+Charge
Audits1 audit by 1 firmLast audit Dec 2022, by SolidProof.
Critical findingsNo open critical findingsIn 1 report.
Open C+Charge’s security recordSecurity firm
SolidProof1,127 projects reviewed · 1,478 reports · latest Feb 2025
See SolidProof’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