withastro/astro: technical due diligence, read from its repository

The median source file here is 30 lines. 7 files exceed 1,000 lines, the largest being 3,657. 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/astro/playwright.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.

5 files were marked deprecated over two years ago and still are, the oldest since Apr 2022. A deprecation is a promise to remove. Ask what still depends on these, and whether removing them is scheduled.

The newest pre-release, astro@7.4.0-beta.1, is not on the branch this survey read; the newest release on it is astro@7.3.5. The shipped product may differ from what this report describes. Survey the release branch too.

22 places set HTML from a value that is neither a literal nor passed through a sanitiser. Where the value can come from a user, that is stored cross-site scripting, and it is the first thing a buyer's security review looks for in a frontend.

Third-party code is committed into this repository without any statement of the terms it arrived under. Unknown terms are harder to deal with than inconvenient ones: an awkward licence can be complied with, an absent one cannot. Each of these needs its origin established before the code changes hands.

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.