Read 2026-10-23
debug-js/debug: technical due diligence, read from its repository
What Borehole read in debug-js/debug's code and history at 666dbc5: 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.
| Dimension | Rating |
|---|---|
| Architecture & Codebase — including AI provenance | not assessable |
| Engineering Process & SDLC Maturity | strong |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
Architecture & Codebase — including AI provenance
not assessableNot rated: only 5 of 11 checks could reach a conclusion here; the rest do not apply to this repository or could not read it.
Engineering Process & SDLC Maturity
strongNo finding.
Product & Engineering Maturity
adequateChange keeps returning to the same few files
adequateFive files out of 68 absorb 45% of all file-level change. Concentration like this is where debt is usually being serviced rather than repaid: the same code is reopened because it is load-bearing, fragile, or both. A repository cannot tell you which — that is a conversation with the team.
package.json — 137 commits touched it |
component.json — 52 commits touched it |
browser.js — 48 commits touched it |
Readme.md — 43 commits touched it |
debug.js — 42 commits touched it |
Security & Reliability Posture
strong13 dependencies float, and no lockfile is committed
adequateDependency versions are declared as ranges and no lockfile is committed, so a build today does not necessarily produce what a build last month produced. That matters twice over in a transaction: the thing being bought cannot be reproduced exactly, and a compromised upstream release arrives without anyone choosing to take it.
package.json:34 — ^2.1.3 |
package.json:37 — ^2.0.1 |
package.json:38 — ^16.2.3 |
package.json:39 — ^3.0.2 |
package.json:40 — ^3.1.4 |
1 advisory against this project in the last 24 months, 1 high or critical
adequateThe newest was published on 2025-09-08. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. None of them affects the surveyed version. The record is incomplete: NVD: 377 records name debug with nothing tying them to this repository (CVE-2006-6581, CVE-2008-4800, CVE-2012-5564, …).
| 2025-09-08: GHSA-4x49-vf9v-38px (high), fixed in 4.4.3: debug@4.4.2 contains malware after npm account takeover |
Observability & Operations
not assessableNot rated: only 3 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on debug-js/debug: 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.