toeverything/affine: technical due diligence, read from its repository

The median source file here is 57 lines. 43 files exceed 1,000 lines, the largest being 8,642. 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/backend/server/src/core/doc/__tests__/codec-compare.spec.ts). 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.

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

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

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

22 of 3,937 locked dependencies match 29 published advisories in OSV, 2 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.

15 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 root licence changed 2 time(s). Code taken under earlier terms stays under them; check which terms any fork or customer relied on.

The newest was published on 2026-07-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: 3 records name AFFiNE with nothing tying them to this repository (CVE-2025-11945, CVE-2026-7702, CVE-2026-99085).