flowchart.js is a browser-side JavaScript library that converts a compact textual DSL into SVG flowcharts rendered via Raphael. The public API is `FlowChart.parse(input)`, which returns a chart object exposing `drawSVG(container, options)`, `clean()`, and `options()`. The DSL defines nodes (`key => symbolType: text`), edges (`a->b`), conditional/parallel branch labels (`yes`, `no`, `path1`-`path3`), inline line-style overrides (`@> {json}`), clickable links (`:>`), click handlers (`:$ functionName`), and flowstate styling suffixes (`|state`). It ships as a UMD bundle with an optional jQuery plugin providing `init`, `setFlowStateByParam`, and `clearFlowState`, plus TypeScript definitions in `types/index.d.ts`. Architecturally it is a cleanly layered monolith: `src/flowchart.parse.js` is a line-based regex state machine that builds the symbol/connection graph; `src/flowchart.chart.js` manages the Raphael paper, bounds, and recursive rendering; a base `Symbol` class in `src/flowchart.symbol.js` handles text layout, attribute resolution, and connector routing; and nine symbol subclasses (`start`, `end`, `operation`, `input`, `output`, `inputoutput`, `subroutine`, `condition`, `parallel`) supply shape-specific anchor points. The most sophisticated piece is the connector router, which detects line-segment intersections and splices cubic Bézier detours to avoid overlaps. Attribute precedence is also well designed: flowstate options override symbol-type options, which override global options. However, the codebase is a webpack 1.x/ESLint 4.x-era ES5 project (engines: Node >= 4.0.0) with only Raphael 2.3.0 pinned as a runtime dependency and no unit tests (`npm test` runs lint only). It carries observable debt: a hardcoded `centerText = false` making a label-positioning branch dead code, a latent variable-shadowing bug in `getNextPath` (uses outer `flowSymb` instead of its argument), a `lineWith` typo, commented-out symbol implementations, and fragile `JSON.parse` on user-supplied line-style text. The release bundle's copyright year is regenerated from the current year at build time, which explains the recent 2026 commit despite no substantive development activity. It is a historically important, once-widely-used library (8.7k stars) that remains functional for its niche, but modern consumers should treat it as legacy and expect to vendor, modernize, or replace it.