ChronoLibrary audit
Oak Security reviewed ChronoLibrary (ChronoLibrary audit) on 22 Sep 2025: 19 findings, 0 critical; 17 marked fixed, 2 acknowledged.
Report hosted on GitHub.
Trustblock does not review code.
Findings19
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 4 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 2 | 13 |
Marked Informational by the firm. Not counted as findings.
InformationalgetCurrentBlockHeight should return a number instead of a string for the block heightAcknowledged
The report gives no description here.
InformationalMemo parser handling of quotes may lead to unexpected resultsAcknowledged
The report gives no description here.
InformationalMissing configuration validation may cause runtime failuresAcknowledged
The report gives no description here.
InformationalUnused configuration parameters create unnecessary complexityAcknowledged
The report gives no description here.
InformationalUse configurable values instead of hardcoded constantsAcknowledged
The report gives no description here.
InformationalUse of any type reduces type safety and code clarityAcknowledged
The report gives no description here.
InformationalGeneric error message masks root causeFixed
The report gives no description here.
InformationalHardcode the last_block row ID in the select and update statements to prevent interacting with the wrong row in the SQLite databaseFixed
The report gives no description here.
InformationalHardcoded API endpoint assumptionsFixed
The report gives no description here.
InformationalInconsistent function description may lead to confusionFixed
The report gives no description here.
Show 7 more
InformationalInconsistent parameter types across API functionsFixed
The report gives no description here.
InformationalIncorrect documentation may mislead developersFixed
The report gives no description here.
InformationalLimited support for nested authz MsgExec transactionsFixed
The report gives no description here.
InformationalLimited Unicode encoding support may cause incomplete decodingFixed
The report gives no description here.
InformationalOutdated dependency versions may introduce security vulnerabilitiesFixed
The report gives no description here.
InformationalThe incremental ID starts at two, which may confuse developers expecting standard indexingFixed
The report gives no description here.
InformationalUnused lastAction variable may confuse application developersFixed
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.
Part of ChronoLibrary’s security record
Security firm
Oak Security33 projects reviewed · 60 reports · latest May 2026
See Oak Security’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