The static workflows parse source into a syntax model. An expression such as run(...) is kept as opaque text: compared as raw bytes, copied verbatim, and never called. When a static override would have to reach inside an opaque expression, JinDistill refuses with UnflattenableDefinitionException or UndiffableDefinitionException rather than guessing.

Static locks store literal and opaque source values in readable JSON. Treat lock contents as sensitive if Jin source contains secrets. fromJson() validates schema, node types, nesting, size, and locations. Capture rejects unresolved inheritance and dynamic removals so an incomplete source graph cannot report unchanged. The caller controls lock reads, writes, and sync timing; toJson() only returns text.

Dotink's parser resolves Jin functions while parsing:

• run(...) executes arbitrary PHP.
• env(...) reads process environment variables, which commonly hold credentials.
• file(...) and --extends read files from disk.
• Any function registered through EvaluationOptions or a caller-provided JinEvaluator runs with your privileges.

Evaluate only configuration you trust. Treat evaluateFile() on attacker-controlled Jin as equivalent to running attacker-supplied PHP.

Source\FilesystemSourceLoader takes a Source\PathPolicy listing allowed roots and refuses any load outside them, so --extends cannot walk out of the directory you permitted. Formatting\ExtendsReference throws InvalidPathException when a parent lies outside the configured application root.

Analysis\AnalysisLimits bounds source bytes, syntax depth, inheritance depth, and collected diagnostics. Exceeding any of them throws AnalysisLimitException before more work is done. Defaults are generous; lower them when analyzing untrusted input.

Reporting\ReportSerializer never emits evaluated values unless the caller passes new ReportOptions(includeValues: true). By default an evaluated report carries only the JSON Pointer and the value's type:

{"path": "/database/password", "type": "string"}

Source-only reports have no values key at all. Diagnostics and verification results reference paths, never values.

verifySemantics() parses two sources with Dotink and compares the resolved data. It is opt-in and executes both inputs, so run it only on trusted configuration — typically to confirm that a normalized or flattened file still resolves the way the original did. Inheritance directives (--extends, --without) are excluded from the comparison because they describe composition, not configuration.

verifyFileSemantics() performs the same comparison but reads the original from disk and supplies its path to the parser. A caller-provided evaluator is outside JinDistill's PathPolicy; its parser functions must enforce any needed filesystem restrictions themselves.

Open a security advisory on the repository rather than a public issue.