sveltejs/kit: technical due diligence, read from its repository

The median source file here is 8 lines. 2 files exceed 1,000 lines, the largest being 4,157. 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.

The suite is configured to retry failing tests (packages/adapter-bun/test/utils.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.

Deleted lines per line added rose from 0.59 to 0.87 between the first and second halves of this history. Rework is normal and often healthy, but a rising ratio means an increasing share of the team's time is spent replacing code that already exists rather than building what does not. Whether that is deliberate repayment or churn is a question for the team.

The newest was published on 2026-07-29. A project that publishes advisories is telling its users about its fixes, and the count and pace say how much security work it carries. Whether 15 of them are fixed in the code you ship could not be told from this history. Answer lives in: the release you run, set against each fixed version.

Nothing in the service initialises an error reporter (Sentry, Rollbar, Bugsnag, Honeybadger or an APM agent). An exception in production reaches a person only if someone is reading the logs, which usually means a customer reports it first.