storybookjs/storybook: technical due diligence, read from its repository

The median source file here is 51 lines. 18 files exceed 1,000 lines, the largest being 26,727. 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 (code/core/src/csf-tools/ConfigObject.test.ts); 3 tests are individually marked to retry. 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.

The newest release, v10.6.5, is not on the branch this survey read; the newest release on it is v10.6.0. The shipped product may differ from what this report describes. Survey the release branch too. This was read from the most recent 50,000 commits (22 Apr 2022 to 3 Nov 2026) only; older history was not read.

.env is tracked in git. Environment files are where credentials usually live, and committing one usually means nobody decided how secrets reach the running application. Whatever is in it is in the history for good. Check 05.1 says whether it holds anything credential-shaped.

3 places run a command through a shell (`shell=True`, `os.system`, `exec` with a template) rather than passing arguments. Where any part comes from outside, it is command injection. Ask where each one's input comes from.

74 of 3,408 locked dependencies match 198 published advisories in OSV, 108 of them rated high or critical. A lockfile says which version is installed, not whether the flawed code is reachable from this product, so each needs a look. Most are fixed by an upgrade, and the advisory names the version. This lockfile pins development tools alongside what ships and does not say which is which, so some of these may never reach a user.

49 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.

The newest was published on 2026-10-12. 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 2 of them are fixed in the code you ship could not be told from this history: its version is only known to be at least 10.6.0. Answer lives in: the release you run, set against each fixed version.