graphsight-langgraph 0.1.3__tar.gz → 0.1.4__tar.gz

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (16) hide show
  1. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/PKG-INFO +11 -5
  2. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/README.md +10 -4
  3. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/PKG-INFO +11 -5
  4. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/pyproject.toml +1 -1
  5. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/LICENSE +0 -0
  6. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph/__init__.py +0 -0
  7. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph/github_ingest.py +0 -0
  8. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph/mapper.py +0 -0
  9. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph/schema.py +0 -0
  10. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph/tracer.py +0 -0
  11. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/SOURCES.txt +0 -0
  12. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/dependency_links.txt +0 -0
  13. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/entry_points.txt +0 -0
  14. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/requires.txt +0 -0
  15. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/graphsight_langgraph.egg-info/top_level.txt +0 -0
  16. {graphsight_langgraph-0.1.3 → graphsight_langgraph-0.1.4}/setup.cfg +0 -0
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: graphsight-langgraph
3
- Version: 0.1.3
3
+ Version: 0.1.4
4
4
  Summary: X-ray for LangGraph retrieval: one callback handler captures every retriever call, score, and relational path — rendered as an interactive graph.
5
5
  Author: Arush Karnatak
6
6
  License: MIT
@@ -94,14 +94,20 @@ graphsight-github-trace REPO [QUESTION] [options]
94
94
  | `--token` | `$GITHUB_TOKEN` | GitHub token. Required for private repositories; raises the rate limit on public ones. |
95
95
  | `--prs` | `25` | Recent pull requests to fetch. |
96
96
  | `--issues` | `25` | Recent issues to fetch. |
97
+ | `--commits` | `25` | Recent commits to fetch — solo repos with no PRs/issues still produce a full graph. |
97
98
  | `--top` | `10` | Items the retrieval keeps. |
98
99
  | `--out` | `graphsight_out/` | Output directory for `agent_trace.json` and `trace_state.json`. |
99
100
 
100
101
  Method note: the CLI builds a corpus with relational edges
101
- (`person AUTHORED pr`, `pr RESOLVES issue`, `pr TOUCHES repo`) and ranks by
102
- **lexical overlap with 1-hop graph expansion** — deliberately simple, and
103
- reported as such. The scores you see are exactly the scores computed;
104
- nothing is presented as semantic similarity.
102
+ (`person AUTHORED pr/commit`, `pr RESOLVES issue`, `pr TOUCHES repo`) and
103
+ ranks by **lexical overlap with 1-hop graph expansion** — deliberately
104
+ simple, and reported as such. The scores you see are exactly the scores
105
+ computed; nothing is presented as semantic similarity.
106
+
107
+ Ask it *who / what / when* questions ("who touched auth recently?", "which
108
+ issue needed two attempts?") — that's what commit and PR history can answer.
109
+ *How-does-it-work* questions need semantic retrieval over code and docs,
110
+ which this deliberately simple demo does not pretend to do.
105
111
 
106
112
  ## Tracing your own agent
107
113
 
@@ -67,14 +67,20 @@ graphsight-github-trace REPO [QUESTION] [options]
67
67
  | `--token` | `$GITHUB_TOKEN` | GitHub token. Required for private repositories; raises the rate limit on public ones. |
68
68
  | `--prs` | `25` | Recent pull requests to fetch. |
69
69
  | `--issues` | `25` | Recent issues to fetch. |
70
+ | `--commits` | `25` | Recent commits to fetch — solo repos with no PRs/issues still produce a full graph. |
70
71
  | `--top` | `10` | Items the retrieval keeps. |
71
72
  | `--out` | `graphsight_out/` | Output directory for `agent_trace.json` and `trace_state.json`. |
72
73
 
73
74
  Method note: the CLI builds a corpus with relational edges
74
- (`person AUTHORED pr`, `pr RESOLVES issue`, `pr TOUCHES repo`) and ranks by
75
- **lexical overlap with 1-hop graph expansion** — deliberately simple, and
76
- reported as such. The scores you see are exactly the scores computed;
77
- nothing is presented as semantic similarity.
75
+ (`person AUTHORED pr/commit`, `pr RESOLVES issue`, `pr TOUCHES repo`) and
76
+ ranks by **lexical overlap with 1-hop graph expansion** — deliberately
77
+ simple, and reported as such. The scores you see are exactly the scores
78
+ computed; nothing is presented as semantic similarity.
79
+
80
+ Ask it *who / what / when* questions ("who touched auth recently?", "which
81
+ issue needed two attempts?") — that's what commit and PR history can answer.
82
+ *How-does-it-work* questions need semantic retrieval over code and docs,
83
+ which this deliberately simple demo does not pretend to do.
78
84
 
79
85
  ## Tracing your own agent
80
86
 
@@ -1,6 +1,6 @@
1
1
  Metadata-Version: 2.4
2
2
  Name: graphsight-langgraph
3
- Version: 0.1.3
3
+ Version: 0.1.4
4
4
  Summary: X-ray for LangGraph retrieval: one callback handler captures every retriever call, score, and relational path — rendered as an interactive graph.
5
5
  Author: Arush Karnatak
6
6
  License: MIT
@@ -94,14 +94,20 @@ graphsight-github-trace REPO [QUESTION] [options]
94
94
  | `--token` | `$GITHUB_TOKEN` | GitHub token. Required for private repositories; raises the rate limit on public ones. |
95
95
  | `--prs` | `25` | Recent pull requests to fetch. |
96
96
  | `--issues` | `25` | Recent issues to fetch. |
97
+ | `--commits` | `25` | Recent commits to fetch — solo repos with no PRs/issues still produce a full graph. |
97
98
  | `--top` | `10` | Items the retrieval keeps. |
98
99
  | `--out` | `graphsight_out/` | Output directory for `agent_trace.json` and `trace_state.json`. |
99
100
 
100
101
  Method note: the CLI builds a corpus with relational edges
101
- (`person AUTHORED pr`, `pr RESOLVES issue`, `pr TOUCHES repo`) and ranks by
102
- **lexical overlap with 1-hop graph expansion** — deliberately simple, and
103
- reported as such. The scores you see are exactly the scores computed;
104
- nothing is presented as semantic similarity.
102
+ (`person AUTHORED pr/commit`, `pr RESOLVES issue`, `pr TOUCHES repo`) and
103
+ ranks by **lexical overlap with 1-hop graph expansion** — deliberately
104
+ simple, and reported as such. The scores you see are exactly the scores
105
+ computed; nothing is presented as semantic similarity.
106
+
107
+ Ask it *who / what / when* questions ("who touched auth recently?", "which
108
+ issue needed two attempts?") — that's what commit and PR history can answer.
109
+ *How-does-it-work* questions need semantic retrieval over code and docs,
110
+ which this deliberately simple demo does not pretend to do.
105
111
 
106
112
  ## Tracing your own agent
107
113
 
@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
4
4
 
5
5
  [project]
6
6
  name = "graphsight-langgraph"
7
- version = "0.1.3"
7
+ version = "0.1.4"
8
8
  description = "X-ray for LangGraph retrieval: one callback handler captures every retriever call, score, and relational path — rendered as an interactive graph."
9
9
  readme = "README.md"
10
10
  requires-python = ">=3.10"