# dependency graphs Projects at AI Tinkerers

> Canonical HTML: https://aitinkerers.org/technologies/dependency-graphs
> Markdown URL: https://aitinkerers.org/technologies/dependency-graphs.md
> Technology record last updated: 2026-04-26T05:06:40Z
> Generated: 2026-09-22T22:37:40Z

Dependency graphs map the intricate web of direct and transitive relationships between software components to identify security vulnerabilities and license risks.

Modern applications rely on thousands of upstream packages; a single React project might pull in 1,500 sub-dependencies. Dependency graphs provide the structural visibility needed to manage this complexity by indexing every manifest file (like package.json or go.mod) and lockfile. Tools like GitHub's dependency graph or OWASP Dependency-Check use these maps to alert developers when a specific version of a library, such as Log4j, contains a critical CVE. By visualizing the entire supply chain, teams can pinpoint exactly where a vulnerable component enters their stack and automate the patching process across the entire repository.

- Official technology site: https://github.com/features/security/software-composition-analysis
- Public AI Tinkerers demos and talks: 1
- Result page: 1 of 1

## Recent Public Talks and Demos

### [CodeDB: Building a Code Intelligence Server That Cuts Agent Token Usage](https://singapore.aitinkerers.org/talks/rsvp_YyFDIYV6hPs)

CodeDB is a code intelligence server for AI agents that indexes a codebase once and serves structured answers through MCP, HTTP, and CLI instead of forcing models to repeatedly scan raw files. In this demo, I show how CodeDB uses structural indexing, trigram search, inverted word lookups, dependency graphs, and snapshots to help agents find only the most relevant code context with much lower latency and dramatically fewer tokens.

- Event context: AI Tinkerers Singapore: The Agentic Future & Dev/Eng Workflows — 2026-04-21 — Singapore
- Public talk page: https://singapore.aitinkerers.org/talks/rsvp_YyFDIYV6hPs

## Related Technologies

- [GitHub](https://aitinkerers.org/technologies/github) ([Markdown](https://aitinkerers.org/technologies/github.md)) — 74 public demos
- [HTTP](https://aitinkerers.org/technologies/http) ([Markdown](https://aitinkerers.org/technologies/http.md)) — 14 public demos
- [inverted word indexing](https://aitinkerers.org/technologies/inverted-word-indexing) ([Markdown](https://aitinkerers.org/technologies/inverted-word-indexing.md)) — 1 public demo
- [JSON-RPC](https://aitinkerers.org/technologies/json-rpc) ([Markdown](https://aitinkerers.org/technologies/json-rpc.md)) — 2 public demos
- [MCP](https://aitinkerers.org/technologies/mcp) ([Markdown](https://aitinkerers.org/technologies/mcp.md)) — 129 public demos
- [structural parsing](https://aitinkerers.org/technologies/structural-parsing) ([Markdown](https://aitinkerers.org/technologies/structural-parsing.md)) — 1 public demo
- [trigram indexing](https://aitinkerers.org/technologies/trigram-indexing) ([Markdown](https://aitinkerers.org/technologies/trigram-indexing.md)) — 1 public demo
- [Zig](https://aitinkerers.org/technologies/zig) ([Markdown](https://aitinkerers.org/technologies/zig.md)) — 4 public demos