Borehole · Project · free tier
tonejs/tone.js
Free reading: not for reliance
0e19a85 · 5,567 commits · 509 files
Read 2026-10-23

tonejs/tone.js: technical due diligence, read from its repository

What Borehole read in tonejs/tone.js's code and history at 0e19a85: its licence, security advisories, releases, review practice, tests, dependencies and operations. Every finding cites the file and line it rests on. The full report also covers the team and asks the questions the code cannot answer.

DimensionRating
Architecture & Codebase — including AI provenancestrong
Engineering Process & SDLC Maturitystrong
Product & Engineering Maturitystrong
Security & Reliability Postureadequate
Observability & Operationsnot assessable
Fit with the Acquirernot assessable

What the repository says

  • Releases are cut from another branch than the one surveyed

Architecture & Codebase — including AI provenance

strong

No finding.

Engineering Process & SDLC Maturity

strong
02.16

Tests are retried until they pass

adequate

The suite is configured to retry failing tests (test/web-test-runner.config.js). A retry turns a flaky test green without saying why it failed, so a green build means the tests passed eventually. Ask how many retries a typical run needs, and which tests need them.

Evidence
test/web-test-runner.config.js:72 — test retry

Product & Engineering Maturity

strong
04.62

Releases are cut from another branch than the one surveyed

adequate

The newest release, 15.1.22, is not on the branch this survey read; the newest release on it is 14.7.39. The shipped product may differ from what this report describes. Survey the release branch too.

Evidence
tag 15.1.22

Security & Reliability Posture

adequate
05.2

None of the standard security guard rails are configured

adequate

There is no disclosure policy, no automated dependency updates, no named code owners and no pre-commit configuration. None of these is load-bearing on its own. Their collective absence says that security posture here is whatever the current team happens to remember to do, which is not a posture that survives the team changing.

Evidence
checked 5 kinds of guard rail across 509 tracked files; 0 present
05.27

The build runs third-party code it does not pin

adequate

4 third-party CI actions are referenced by a tag or branch rather than a commit, so they run whatever that tag points to on the day. Tags have been moved to malicious commits in real supply-chain attacks, and a piped script is whatever the server returns that minute. Pinning to a commit is the fix, and it is small.

Evidence
.github/workflows/release.yml:61 — action pinned by tag
.github/workflows/release.yml:138 — action pinned by tag

Observability & Operations

not assessable

Not rated: only 5 of 16 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.

Fit with the Acquirer

not assessable

Not rated: structurally not assessable from a repository.

Read more, or read your own

The full report on tonejs/tone.js: every dimension, the questions for the room, and the audit log.

Survey a repository: free on public repositories. Private code is read on your own machine by a collector whose source you can read first.