Lineage Explorer

A React-based visualization tool for exploring data lineage and computational integrity. Part of the EQTYlab ecosystem, it displays data provenance chains showing how data flows through computational systems, which actors are involved, and what verification statements are attached.

Features

• Interactive Graph Visualization: Drag-to-explore canvas with zoom/pan controls using ReactFlow
• Detailed Inspector: Sidebar showing registration, governance, storage, and signature details for selected nodes
• Dual Operating Modes:
  • Manifest Viewer: Upload or select sample manifest JSON files to explore
  • Integrity Service: Auth0-integrated mode for querying a backend integrity service

Prerequisites

This project uses Nix for development environment management. Install Nix, then the devshell will provide all required dependencies.

Alternatively, ensure you have installed:

• Node.js
• pnpm

Local Development

# Enter the Nix development shell (if using Nix)
nix develop

# Install dependencies
pnpm install

# Start development server
pnpm dev

Available Commands

| Command | Description | | --------- | ------------- | | pnpm dev | Start development server | | pnpm build | Build both app and library | | pnpm build:app | Build standalone application | | pnpm build:lib | Build npm package | | pnpm fmt | Format code with Prettier | | pnpm format:check | Check code formatting | | pnpm lint | Run ESLint | | pnpm lint:fix | Run ESLint with auto-fix | | pnpm typecheck | Run TypeScript type checking |

Build Outputs

The project produces two build artifacts:

1. Standalone App (dist/app/): Deployed to https://explorer.eqtylab.io
2. NPM Package (dist/lib/): Published to npm as @eqtylab/explorer

Release

Releases are automated via GitHub Actions and triggered by bumping the version in package.json on main.

How to Release

1. Bump version in package.json (e.g. 0.10.2 -> 0.10.3)
2. Open a PR and merge it to main

When the change lands on main, the Release workflow will automatically:

• Tag the commit as v<version> and create a GitHub Release with generated notes
• Call the Publish workflow to build and publish to npm

A version containing a hyphen (e.g. 0.11.0-rc1) is marked as a GitHub pre-release. Note that npm still publishes it under the latest dist-tag.

Version Management

package.json is the single source of truth for the version. If the tag v<version> already exists, the release workflow does nothing.

Publishing can also be triggered manually:

• Publish via Run workflow builds and packs without publishing (--dry-run by default; uncheck to publish the version currently in package.json)
• Creating a GitHub Release by hand still publishes the version from its tag

Configuration

See the configuration documentation for customization options.

Adding Example Manifests

1. Add the manifest JSON file to ./public/manifests
2. Update the manifests section in ./src/app/config.json
   • The name must match the filename without the extension