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 |
HighBlocks are repeatedly processed, resulting in potentially incorrect state updatesFixed
The report gives no description here.
HighIncompatible Action interfaces may cause integration failuresFixed
The report gives no description here.
HighLack of network error handling breaks API rotationFixed
The report gives no description here.
HighLeaked database connections may cause resource exhaustionFixed
The report gives no description here.
LowFailure fetching batches can cause an infinite retry loopFixed
The report gives no description here.
LowInconsistent inclusion or exclusion of empty arguments in extractMemoContent may lead to confusionFixed
The report gives no description here.
LowIncorrect test expected values cause validation against the wrong parametersFixed
The report gives no description here.
LowIncorrect usage of expect in vitest causes tests to never failFixed
The report gives no description here.
LowLack of action ordering check may cause state corruptionFixed
The report gives no description here.
LowMalicious transaction memo may cause the indexer to haltFixed
The report gives no description here.
Show 7 more
LowNo check on the returned value of findIndexFixed
The report gives no description here.
LowNo verification on the namespace may lead to state corruptionFixed
The report gives no description here.
LowNon-robust cloning method may cause data corruptionFixed
The report gives no description here.
LowPrototype pollution allows crafted memos to bypass validationFixed
The report gives no description here.
LowUnclear message filter logic may cause unexpected transaction inclusionFixed
The report gives no description here.
LowUnhandled exception in base64ToArrayBuffer function may cause application crashesFixed
The report gives no description here.
LowUnhandled JSON.stringify operations may cause process crashesFixed
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