weavatrix - npm Package Compare versions

Comparing version

1.1.2

1.2.0

+3

-3

package.json

		{
		"name": "weavatrix",
		"version": "1.1.2",
		"weavatrixEngineVersion": "2.0.2",
		"description": "Native repository intelligence for coding agents: 39 read-only MCP operations backed by typed evidence graphs, impact, architecture, APIs, Git, search, semantics, and memory.",
		"version": "1.2.0",
		"weavatrixEngineVersion": "2.1.1",
		"description": "Native repository intelligence for coding agents: 42 read-only MCP operations backed by typed evidence graphs, impact, architecture, APIs, Git, search, semantics, and memory.",
		"author": "Sergii Ziborov <sergii.ziborov@gmail.com>",
		@@ -7,0 +7,0 @@ "license": "MIT",

+21

-23

README.md

		@@ -11,3 +11,3 @@ # Weavatrix — native MCP repository intelligence
		Weavatrix is the native MCP product for repository intelligence. It gives
		Codex, Claude Code, and other coding agents 39 read-only operations over one
		Codex, Claude Code, and other coding agents 42 read-only operations over one
		revision-bound evidence graph: impact, architecture, APIs, Git history,
		@@ -23,2 +23,4 @@ duplicates, dead code, search, semantic links, and temporal memory.
		JavaScript engine; both registry packages run the same Rust adapter and engine.
		The separately versioned `weavatrix-js` package is a legacy compatibility
		implementation and is not bundled here.

		@@ -77,9 +79,9 @@ ## Install in 30 seconds

		## The 39 read-only operations
		## The 42 read-only operations

		\| Workflow \| Operations \|
		\| --- \| --- \|
		\| Graph orientation \| `graph_stats`, `get_node`, `get_neighbors`, `query_graph`, `god_nodes`, `shortest_path`, `get_community`, `list_communities`, `module_map` \|
		\| Change impact \| `get_dependents`, `change_impact`, `verified_change`, `prepare_change`, `graph_diff` \|
		\| Exact source context \| `search_code`, `read_source`, `inspect_symbol`, `context_bundle` \|
		\| Graph orientation \| `graph_stats`, `get_node`, `get_neighbors`, `query_graph`, `god_nodes`, `shortest_path`, `get_community`, `list_communities`, `module_map`, `build_graph` \|
		\| Change impact \| `get_dependents`, `change_impact`, `select_tests`, `verified_change`, `prepare_change`, `graph_diff` \|
		\| Exact source context \| `search_code`, `read_source`, `inspect_symbol`, `context_bundle`, `map_stacktrace` \|
		\| Health and quality \| `find_duplicates`, `find_dead_code`, `run_audit`, `coverage_map`, `hot_path_review` \|
		@@ -114,8 +116,8 @@ \| APIs and transports \| `list_endpoints`, `trace_endpoint`, `trace_api_contract` \|
		v
		weavatrix 1.1.2
		weavatrix 1.2.0
		profile catalog · refresh · watcher · MCP framing
		\|
		v
		weavatrix-rust 2.0.2
		typed graph · analysis · 39 read-only operations
		weavatrix-rust 2.1.1
		typed graph · analysis · 42 read-only operations
		```
		@@ -129,6 +131,6 @@

		Engine 2.0.2 keeps `find_duplicates` families internally consistent after
		test/classified/low-signal filters and `top_n` truncation. Families are rebuilt
		from the surviving pairs, so excluded members and dangling pair identifiers
		cannot remain in the result.
		Engine 2.1.1 adds `map_stacktrace`, `select_tests`, `build_graph`,
		`token_budget` on the source-context operations, and dependency-injection
		type evidence, and keeps `find_duplicates` families internally consistent
		after filtering and `top_n` truncation.

		@@ -141,14 +143,10 @@ ## Release evidence

		The packaged 1.1.2 product (`weavatrix-rust` 2.0.2) passed the bounded native
		gate on 2026-07-30: 39 tools; cold initialize 405.770 ms; `tools/list`
		0.790 ms; first `graph_stats` 54.880 ms; and 1,000 hot `graph_stats`
		calls at 136.83 calls/s with 0 failures, p50 7.610 ms, p95
		10.180 ms, and p99 12.230 ms.
		The packaged 1.2.0 product (`weavatrix-rust` 2.1.1) was measured on 2026-08-03
		against installed `weavatrix-js` 0.3.15 on a real JavaScript service
		repository: paired cold-boundary median 32.06x (spawn to first tool
		result: 157.34 ms vs 5,068.22 ms) and warm tools/call median 36.85x
		(7.94 ms vs 292.55 ms), passing the 24x cold and 30x warm release
		thresholds and sitting slightly above the 30.34x recorded for the 1.0.0
		baseline.

		The last published baseline (`weavatrix` 1.0.0 versus `weavatrix-js` 0.3.15)
		measured a 30.34x median cold-boundary ratio and 156.10x warm-call
		ratio. Those comparison numbers remain historical and are not presented as a
		fresh competitor benchmark; the current 1.1.2 gate is bounded and does not
		relabel them.

		Full evidence and methodology:
		@@ -155,0 +153,0 @@ [benchmarks](https://github.com/sergii-ziborov/weavatrix/blob/main/docs/benchmarks.md).

+3

-3

server.json

		@@ -5,3 +5,3 @@ {
		"title": "Weavatrix",
		"description": "Native Weavatrix MCP: 39 read-only repository tools across 24 code and configuration surfaces.",
		"description": "Native Weavatrix MCP: 42 read-only repository tools across 24 code and configuration surfaces.",
		"repository": {
		@@ -11,3 +11,3 @@ "url": "https://github.com/sergii-ziborov/weavatrix",
		},
		"version": "1.1.2",
		"version": "1.2.0",
		"websiteUrl": "https://weavatrix.com",
		@@ -19,3 +19,3 @@ "packages": [
		"identifier": "weavatrix",
		"version": "1.1.2",
		"version": "1.2.0",
		"runtimeHint": "npx",
		@@ -22,0 +22,0 @@ "transport": {

+10

-0

skill/references/tool-routing.md

		@@ -7,2 +7,4 @@ # Tool routing
		- `module_map`, `list_communities`, `get_community`, `god_nodes`: topology.
		- `build_graph`: workspace aggregators, members, targets, and runner
		configurations from manifest evidence; no build tool runs.
		- `get_node`, `get_neighbors`, `inspect_symbol`, `context_bundle`: exact
		@@ -12,2 +14,8 @@ entities and local evidence.
		- `search_code`, `read_source`: lexical and source confirmation.
		- `map_stacktrace`: paste a Node, JVM, Python, or Rust stack trace; frames map
		to repository files and the nearest symbol, so debugging starts at the graph
		instead of at a directory listing.
		- Pass `token_budget` on `search_code`, `read_source`, `context_bundle`, or
		`query_graph` to fit the answer into the context window you have left; the
		report states exactly what was dropped.

		@@ -17,2 +25,4 @@ ## Change and history
		- `change_impact`: current diff, explicit files, or supplied patch.
		- `select_tests`: the suites a change most plausibly needs to run, ranked by
		graph distance; static selection, no coverage run consumed.
		- `graph_diff`: structural comparison with an immutable Git revision.
		@@ -19,0 +29,0 @@ - `git_history`: churn and co-change in one repository.

bin/native/darwin-arm64/weavatrix