frappe/erpnext: technical due diligence, read from its repository

The median source file here is 29 lines. 74 files exceed 1,000 lines, the largest being 3,970. 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 newest release, v16.52.1, is not on the branch this survey read; the newest release on it is v13.9.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 (12 Apr 2016 to 22 Oct 2026) only; older history was not read.

banking/.env.production 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.

4 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; 1 step pipes a download straight into a shell. 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.

8 of 457 locked dependencies match 32 published advisories in OSV, 19 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.

8 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 165 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 13.9.0. Answer lives in: the release you run, set against each fixed version. GHSA-5wpj-6rvp-9ff7 (high), GHSA-3x6c-gc4v-f5v8 (moderate), GHSA-qq49-v74j-hjh7 (critical) and 4 more are fixed in the surveyed commit; which release carries them cannot be told from this history, which does not place the release users run. Answer lives in: the version you run. The record is incomplete: NVD: 20 records name erpnext with nothing tying them to this repository (CVE-2018-3882, CVE-2018-3883, CVE-2018-3884, …).