Read 2026-11-07
zloirock/core-js: technical due diligence, read from its repository
What Borehole read in zloirock/core-js's code and history at 8571f75: 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 | strong |
| Engineering Process & SDLC Maturity | adequate |
| Product & Engineering Maturity | adequate |
| Security & Reliability Posture | strong |
| Observability & Operations | not assessable |
| Fit with the Acquirer | not assessable |
What the repository says
- Releases are cut from another branch than the one surveyed
Architecture & Codebase — including AI provenance
strongCommit messages are templated rather than written
adequate37% of commit subjects are exact repeats of another subject, and subject length varies by only 25.6 characters. A log written by someone explaining their reasoning to a future reader does not look like this. The log is therefore weak evidence of intent, whatever the code is like.
| 1602× 'update dependencies' |
| 138× 'update the changelog' |
| 65× 'some stylistic changes' |
deno/corejs/index.js is 18,396 lines, 2628× this codebase's median file
adequateThe median source file here is 7 lines. 3 files exceed 1,000 lines, the largest being 18,396. Size is not a defect on its own — some problems genuinely live in one place — but these are where merge conflicts, review fatigue and single-owner knowledge concentrate, and they are the first thing that slows an inheriting engineer down.
deno/corejs/index.js:1 — 18,396 lines (2628× median) |
packages/core-js-compat/src/data.mjs:1 — 3,406 lines (486× median) |
packages/core-js/modules/web.url.constructor.js:1 — 1,167 lines (166× median) |
Engineering Process & SDLC Maturity
adequateLittle of the recent change carries a trace of review
adequateIn the last 24 months, 132 of 1,644 commits (8.0%) carry any trace of review: a merge, a pull-request reference, a Reviewed-by or Reviewed-on trailer, a Closes/Fixes reference, a maintainer's sign-off on someone else's change, or a change applied by someone other than its author. That is low but not absent. Review may happen in a workflow this history does not record; a buyer should ask how change is approved before it ships.
| 132 of 1,644 commits in the last 24 months carry review evidence; 9.5% across all 7,963 |
Product & Engineering Maturity
adequate553 unresolved debt markers, 4.0 per thousand lines
adequateThe codebase carries 553 TODO, FIXME, HACK or XXX markers across 138,913 lines. These are the team's own notes about work they knew was unfinished. A high density is not automatically bad — it can mean an honest team — but every one of them is a decision deferred, and after an acquisition they are deferred onto someone who was not in the room.
deno/corejs/index.js:2361 — // TODO: Remove this module from `core-js@4` since it's replaced to module below |
deno/corejs/index.js:3439 — // TODO: Replace with module dependency in `core-js@4` |
deno/corejs/index.js:7032 — // TODO: Remove this module from `core-js@4` since it's split to modules listed below |
deno/corejs/index.js:10741 — /* eslint-disable max-statements, max-depth -- TODO */ |
deno/corejs/index.js:10843 — // TODO: use `Object.create(null)` in `core-js@4` |
Releases are cut from another branch than the one surveyed
adequateThe newest pre-release, v4.0.0-alpha.1, is not on the branch this survey read; the newest release on it is v3.51.0. The shipped product may differ from what this report describes. Survey the release branch too.
| tag v4.0.0-alpha.1 |
Security & Reliability Posture
strongThe build runs third-party code it does not pin
adequate4 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.
.github/workflows/build-bundles.yml:31 — action pinned by tag |
.github/workflows/build-website-for-branch.yml:25 — action pinned by tag |
Observability & Operations
not assessableNot 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 assessableNot rated: structurally not assessable from a repository.
Read more, or read your own
The full report on zloirock/core-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.