All 168 Dependencies
Every package Enso depends on, ranked by repo health score.
Enso is a self-service data preparation and analysis platform aimed at data teams in finance, accounting, and revenue operations who need repeatable pipelines without writing (or being locked out of) code. What sets it apart architecturally is that its visual node-graph editor and its textual Enso language are two renderings of the exact same parsed AST rather than a one-way canvas-to-code export: a shared Rust parser compiles to WebAssembly for the desktop GUI and to a native JNI library for the JVM engine, with generated Java bindings keeping both sides in lockstep. Editing a node updates the source, and editing the source updates the graph.
Under the hood, the Enso Engine is a Scala/Java codebase running on GraalVM, using a Truffle-based interpreter and JIT compiler so that live edits to a pipeline re-execute with near-native interactive speed instead of a full batch re-run. The standard library (distribution/lib/Standard/, backed by std-bits/ Java helpers) ships built-in connectors for Snowflake, DuckDB, AWS, Google Cloud, Microsoft, and Tableau, so workflows can pull from and land in real data platforms rather than staying local-only.
The desktop IDE is an Electron application built from a pnpm/TypeScript monorepo, mixing a Vue 3 graph editor (the direction the project is moving) with a still-present React-based dashboard for project and cloud account management. A ydoc-server layer backs real-time multiplayer editing for Enso Cloud, which is metered by Free/Solo/Team/Enterprise plans.
Licensing is split rather than singular: the Enso Engine (interpreter, compiler, language server, CLI) is Apache-2.0, the IDE (app/gui) is AGPL-3.0, and the pre-built downloadable binaries are covered by a separate commercial EULA (with no-cost licenses available to individuals and small companies) — so "self-hosted and free" and "open source" aren't quite the same claim here.