|Project Name||Stars||Downloads||Repos Using This||Packages Using This||Most Recent Commit||Total Releases||Latest Release||Open Issues||License||Language|
|Neo4j||12,002||966||186||10 days ago||423||November 24, 2023||293||gpl-3.0||Java|
|Graphs for Everyone|
|Cartography||2,771||3 days ago||150||December 01, 2023||104||apache-2.0||Python|
|Cartography is a Python tool that consolidates infrastructure assets and the relationships between them in an intuitive graph view powered by a Neo4j database.|
|Pygraphistry||1,939||4||2||3 days ago||163||November 02, 2023||151||bsd-3-clause||Python|
|PyGraphistry is a Python library to quickly load, shape, embed, and explore big graphs with the GPU-accelerated Graphistry visual graph analyzer|
|Neovis.js||1,403||3||4||2 months ago||30||May 23, 2023||48||apache-2.0||TypeScript|
|Neo4j + vis.js = neovis.js. Graph visualizations in the browser with data from Neo4j.|
|Spigo||1,105||7 years ago||1||December 20, 2016||43||apache-2.0||Go|
|Simulate Protocol Interactions in Go|
|Node Neo4j||934||459||55||5 years ago||34||June 11, 2015||46||apache-2.0||CoffeeScript|
|[RETIRED] Neo4j graph database driver (REST API client) for Node.js|
|InteractiveGraph provides a web-based interactive visualization and analysis framework for large graph data, which may come from a GSON file, or an online Neo4j graph database. InteractiveGraph also provides applications built on the framework: GraphNavigator, GraphExplorer and RelFinder.|
|Stock Knowledge Graph||896||3 years ago||15||mit||Python|
|Neomodel||850||62||15||14 days ago||51||November 02, 2023||63||mit||Python|
|An Object Graph Mapper (OGM) for the Neo4j graph database.|
|Kuzu||759||10 hours ago||41||December 03, 2023||242||mit||C++|
|Embeddable property graph database management system built for query speed and scalability. Implements Cypher.|
Cartography is a Python tool that consolidates infrastructure assets and the relationships between them in an intuitive graph view powered by a Neo4j database.
Cartography aims to enable a broad set of exploration and automation scenarios. It is particularly good at exposing otherwise hidden dependency relationships between your service's assets so that you may validate assumptions about security risks.
Service owners can generate asset reports, Red Teamers can discover attack paths, and Blue Teamers can identify areas for security improvement. All can benefit from using the graph for manual exploration through a web frontend interface, or in an automated fashion by calling the APIs.
Cartography is not the only security graph tool out there, but it differentiates itself by being fully-featured yet generic and extensible enough to help make anyone better understand their risk exposure, regardless of what platforms they use. Rather than being focused on one core scenario or attack vector like the other linked tools, Cartography focuses on flexibility and exploration.
You can learn more about the story behind Cartography in our presentation at BSidesSF 2019.
#cartographyon the Lyft OSS Slack.
Thank you for considering contributing to Cartography!
Legal stuff: This project is governed by Lyft's code of conduct. All contributors and participants agree to abide by its terms.
Submit a GitHub issue to report a bug or request a new feature. If we decide that the issue needs more discussion - usually because the scope is too large or we need to make careful decision - we will convert the issue to a GitHub Discussion.
Get started with our developer documentation. Please feel free to submit your own PRs to update documentation if you've found a better way to explain something.
We require a CLA for code contributions, so before we can accept a pull request we need to have a signed CLA. Please visit our CLA service and follow the instructions to sign the CLA.
If your organization uses Cartography, please file a PR and update this list. Say hi on Slack too!