anvaka/ngraph.path

Path finding in a graph

View on GitHub ↗Jump to charts ↓

anvaka/ngraph.path has 3k+ stars and 150+ forks on GitHub, is written in JavaScript, and was last pushed on Jul 27, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on September 10th, 2017
Open Issues & Pull Requests: 18 (+0)
GitHub issues: Enabled
Number of forks: 189
Total Stargazers: 3,134 (+0)
Total Subscribers: 59 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 22.5 hours
Mean response time: 25.3 hours
90th percentile: 28.2 hours
Tracked items: 2

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 2
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,537 days
Stale 30+ days: 2
Stale 90+ days: 2

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

ngraph.path is a pathfinding library that finds shortest paths in graphs.

The library solves the problem of efficiently computing routes between nodes in graph structures. It implements multiple pathfinding algorithms including A*, Dijkstra's algorithm, and breadth-first search. The approach allows developers to choose the algorithm best suited to their graph characteristics—A* with heuristics for informed search in spatial graphs, Dijkstra's for unweighted or weighted graphs without heuristics, and breadth-first search for simpler cases. The library uses a heap data structure to optimize algorithm performance.

The tool suits projects that need to find optimal paths through networked data, such as game development, route planning, network analysis, or any application working with graph structures. It is particularly valuable when you need flexibility in algorithm selection rather than a one-size-fits-all solution. The library is designed as a lightweight, focused module rather than a comprehensive graph processing framework, making it appropriate for developers who want pathfinding capabilities without heavy dependencies.

Development on the project shows consistent maintenance with regular updates addressing issues and improvements. The maintainer actively responds to bug reports and feature requests, indicating ongoing engagement with user needs. The codebase receives periodic refinements to algorithm implementations and documentation, suggesting a commitment to code quality and usability.