cartography-cncf/cartography

Cartography is a Python tool that pulls infrastructure assets and their relationships into a Neo4j graph database.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 11 minutes ago
Added to GitGenius on September 17th, 2026
Created on February 27th, 2019
Open Issues & Pull Requests: 132 (+0)
GitHub issues: Enabled
Number of forks: 572
Total Stargazers: 4,092 (+0)
Total Subscribers: 383 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 38.5 hours
Mean response time: 77.7 days
90th percentile: 176.5 days
Tracked items: 312

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 7% of issues opened in the past year have never received a reply. 67% of open issues come from outside the core team, a mix of external reports and the maintainers' own roadmap. Work labelled "confirmed-bug" is answered fastest, typically in about 8 hours, while "keep fresh" waits about 3 weeks. 81% of issues opened in the past year have been closed, leaving a working backlog. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 45
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 631 days
Stale 30+ days: 37
Stale 90+ days: 24

Recent activity

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

Top labels

  • module:AWS (103)
  • data-addition (78)
  • good first issue (44)
  • keep fresh (34)
  • confirmed-bug (29)
  • maintenance (25)
  • module:GCP (23)
  • long-term-improvement (19)

Most active issues this week

Detailed Description

Cartography is a Python tool that pulls infrastructure assets and their relationships into a Neo4j graph database.

Cartography solves the problem of understanding infrastructure sprawl across cloud and on-premises environments by aggregating asset data from multiple sources into a unified graph representation. It connects to cloud providers, container platforms, and other infrastructure systems to extract resources and their relationships, then stores this information in Neo4j where it can be queried and analyzed. This graph-based approach makes it possible to discover connections between assets that would be difficult to identify in siloed systems and to answer complex questions about infrastructure topology and dependencies.

The tool is suited for organizations managing infrastructure across multiple cloud providers or hybrid environments who need visibility into asset relationships and dependencies. It works well for teams building internal tools around infrastructure discovery, compliance checking, and security analysis. Cartography is particularly valuable when you need to correlate data across different infrastructure layers—for instance, understanding which cloud resources are connected to which Kubernetes clusters, or tracing relationships between network components and applications. The Neo4j backend enables flexible querying without requiring predefined schemas, allowing teams to explore their infrastructure in ways that match their specific operational needs.

The project shows consistent development activity with regular updates to support new infrastructure sources and maintain compatibility with evolving cloud platforms. The codebase demonstrates a modular architecture where new data sources can be added as plugins, indicating an established pattern for extending functionality. Documentation is maintained alongside the code, suggesting attention to usability for new adopters. The project maintains active engagement with its user base through issue tracking and appears responsive to requests for additional infrastructure integrations.