ChronoLibrary security record

As of 21 Oct 2026, ChronoLibrary has 1 audit report on Trustblock, by Oak Security, dated 22 Sep 2025. That report lists no open critical findings.

Critical findings
No open critical findings
In 1 report.
Open the latest report
Your label, live
Get the label for your site

Record last updated . It holds audits and findings, contracts and incidents up to Oct 2026. Trustblock does not review code.

Audits1

Newest first

AuditSecurity firmDateScopeCritical findingsReport
ChronoLibrary auditSecurity firm: Oak SecurityDate: Scope: Not recorded (see the report)No open critical findingsOpen · GitHub

Findings19

Statuses are the security firm’s own, from each report.

SeverityOpenAcknowledgedFixed
Critical000
High004
Medium000
Low0213
HighBlocks are repeatedly processed, resulting in potentially incorrect state updatesChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
HighIncompatible Action interfaces may cause integration failuresChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
HighLack of network error handling breaks API rotationChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
HighLeaked database connections may cause resource exhaustionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowFailure fetching batches can cause an infinite retry loopChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowInconsistent inclusion or exclusion of empty arguments in extractMemoContent may lead to confusionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowIncorrect test expected values cause validation against the wrong parametersChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowIncorrect usage of expect in vitest causes tests to never failChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowLack of action ordering check may cause state corruptionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowMalicious transaction memo may cause the indexer to haltChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
Show 7 more
LowNo check on the returned value of findIndexChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowNo verification on the namespace may lead to state corruptionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowNon-robust cloning method may cause data corruptionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowPrototype pollution allows crafted memos to bypass validationChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowUnclear message filter logic may cause unexpected transaction inclusionChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowUnhandled exception in base64ToArrayBuffer function may cause application crashesChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report
LowUnhandled JSON.stringify operations may cause process crashesChronoLibrary audit · Oak Security · 22 Sep 2025Fixed

The report gives no description here.

Open the report

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Show this on your site

Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.

Content

Facts

Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="chronolibrary"
></div>
</body>

Paste the code where the label should appear. It uses no API credit and updates by itself.

Something 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