Skip to workspace
PixelOkay
Dependency Graph Explorer● Browser-local
Tools
DEVELOPER TOOLS GRAPH INTELLIGENCE

Dependency Graph Explorer

Map dependencies, identify cycles, follow impact paths, and understand package or project structures in one private workspace.

Nodes0Components
Connections0Directed links
Cycle groups0Circular groups
Isolated0Disconnected components
Dependency mapEntire project
100%
Drag empty space to pan · Scroll to zoom · Click a node to inspect
LINK TYPES
Ready. Example graph is loaded and all data stays on this device.

Dependency visualization for software projects

Dependency Graph Explorer helps you read package manifests, lockfile relationships, CycloneDX software bills of materials and generic CSV dependency links. Follow direct and transitive dependencies, reveal reverse impact, find directed paths, and detect circular references. You can modify the graph and export editable JSON, CSV, Mermaid, SVG or PNG without a server.

Imports do not execute package scripts or access your repository. A package.json or requirements.txt manifest lists only declared direct dependencies; installed transitive dependencies require a supported lockfile or SBOM. This explorer is not a vulnerability scanner, automatic dependency resolver or security certification tool.

Add component

Create a component and connect it to dependencies.

Using the Dependency Graph Explorer

Start with an example or import a package.json, npm package-lock.json v2/v3, CycloneDX JSON, generic from,to,type CSV, PixelOkay graph JSON, or a simple requirements.txt.

Dependency arrows point from a package to what it requires. Select a node using the graph or the searchable components list. The Details tab lets you edit it; Analyze reveals cycles, reverse impact, shortest directed paths, a QA report, dependency-first groups, and baseline comparisons. The scope control restricts the diagram to a selected component's dependencies or dependents.

Drag empty space to pan; scroll to zoom. Focus the graph and use arrow keys to pan, +/− to zoom, and Home to fit. Use Ctrl/Cmd + Z or Shift + Ctrl/Cmd + Z for undo/redo outside text fields. Exports are local.

Large imports are limited to 2,500 nodes, 12,000 edges and 5 MB. The interactive graph draws up to 230 nodes and 850 edges at once; use focus mode or search for larger projects. The downloaded project retains the entire imported graph. Unsupported files are rejected rather than guessed.

Using Dependency Graph Explorer

Import declared software dependency relationships, inspect downstream impact and strongly connected groups, compare a baseline, and export structural graph reports.

Workflow

  1. Import a supported project manifest or graph file, or start from a dependency CSV and confirm how the relationships are directed.
  2. Select a package or dependency to inspect affected dependents, filters, and strongly connected groups; compare an imported baseline when needed.
  3. Review the graph and report as structural evidence, then export a project or Mermaid/SVG/PNG/CSV summary.

Worked example

Represent app-a as depending on library-b and library-b as depending on parser-c. Select parser-c to inspect downstream dependents, then compare the graph with an earlier manifest and export a Mermaid diagram.

Limits and data handling

Edges point from a dependent to its dependency. Strongly connected component groups do not enumerate every simple cycle. The tool inspects declared relationships and does not resolve live package registries, audit vulnerabilities, or determine license compliance. Confirm the package-manager format and relationship meaning before interpreting impact.

Frequently asked questions

Does the graph install or resolve current packages?

No. It analyzes declared dependency data you import; it does not install packages or resolve them against a live registry.

Does a strongly connected group list every possible cycle?

No. It groups strongly connected components; that is not an enumeration of every simple cycle in the graph.

Related tools