langgenius/dify: technical due diligence, read from its repository

The median source file here is 84 lines. 92 files exceed 1,000 lines, the largest being 6,671. 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 pre-release, 2.0.0-beta.2, is not on the branch this survey read; the newest release on it is 1.18.0. The shipped product may differ from what this report describes. Survey the release branch too.

38 places in product code build SQL by formatting or joining strings rather than passing parameters. 1 of them put a value into the string; in the rest, what the code shows going in is a table or column name, a constant, or something the line does not show. Ask whether any value reaches these strings, rather than a parameter.

2 places read data with a deserialiser that executes what it reads (pickle, `yaml.load` without a safe loader). That is safe on data the system wrote itself and remote code execution on anything else. Ask where each one's input comes from.

LICENSE grants Apache-2.0 with a commercial-licence condition: source available, not open source; some uses need a commercial licence from the licensor. The reading comes from the licence's own title and clauses. Whether the terms fit the buyer's intended use, and whether any paid licence transfers with the code, is a question for counsel and the licensor.

The root licence changed 3 time(s). The latest terms restrict what users, hosts or a buyer may do in ways the earlier ones did not. Code taken under the old terms stays under them, so both matter in diligence.

The newest was published on 2026-09-03. 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 6 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 1.18.0. Answer lives in: the release you run, set against each fixed version. The record is incomplete: NVD: 6 records name dify with nothing tying them to this repository (CVE-2025-0185, CVE-2026-18266, CVE-2026-18632, …).

9 images in the deployment configuration are named without a version or as `latest`. A redeploy can change the software without a commit, a rollback has nothing to roll back to, and nobody can say from the repository what is running.

11 places outside configuration test whether they are running in production or staging. Staging then does not exercise production's code, and each deploy is the first run of those branches. Differences belong in configuration the code reads, not in the code.