weavatrix 0.2.14 → 0.2.16

package/src/security/registry-sig.rules.js

@@ -14,7 +14,7 @@ export const MALWARE_ALLOWLIST = new Set([
 // webhook.site / oast.* / canarytokens / dnslog.cn: Shai-Hulud-era exfil + OOB-callback services.
 const EXFIL_HOSTS = "discord(app)?\\.com/api/webhooks|hooks\\.slack\\.com/services|api\\.telegram\\.org/bot|pastebin\\.com/raw|burpcollaborator|oastify\\.com|oast\\.(pro|live|fun|me|site|online)|interact\\.sh|pipedream\\.net|requestbin|webhook\\.site|canarytokens\\.(com|org)|dnslog\\.cn";
 // external URL that is NOT an exfil endpoint (owned by exfil-url) and NOT a raw IP (owned by exfil-ip)
-const PLAIN_EXTERNAL_URL = `https?://(?!(${EXFIL_HOSTS})|[0-9]{1,3}\\.|localhost\\b|127\\.|0\\.0\\.0\\.0|10\\.|192\\.168\\.|169\\.254\\.|172\\.(1[6-9]|2\\d|3[01])\\.)[^'"\`\\s)\\\\]+`;
+const PLAIN_EXTERNAL_URL = `https?://(?!(${EXFIL_HOSTS})|[0-9]{1,3}\\.|localhost\\b|127\\.|0\\.0\\.0\\.0|10\\.|192\\.168\\.|169\\.254\\.|172\\.(1[6-9]|2\\d|3[01])\\.)[a-z0-9][^'"\`\\s)\\\\]+`;
 
 // ---- content rules (scanned over node_modules file text; `pattern` is ripgrep-safe ERE, `re` is the
 // JS validator used both to classify rg hits and by the no-rg fallback) ----
@@ -181,8 +181,8 @@ export const CONTENT_RULES = [
     severity: "low", // minified/legit code look-alikes — only escalates with a second signal
     nearZeroFp: false,
     noisy: true,
-    pattern: "eval\\(atob\\(|eval\\(Buffer\\.from\\(|_0x[a-f0-9]{4}",
-    re: /eval\(atob\(|eval\(Buffer\.from\([^)]*base64|_0x[a-f0-9]{4,}/,
+    pattern: "eval\\(atob\\(|eval\\(Buffer\\.from\\(|\\b_0x[a-f0-9]{4,}\\b",
+    re: /eval\(atob\(|eval\(Buffer\.from\([^)]*base64|\b_0x[a-f0-9]{4,}\b/,
     what: "obfuscation marker (eval-of-decoded payload / string-array obfuscator)",
   },
 ];

package/src/util.js

@@ -16,6 +16,14 @@ export function uniqueBy(list, keyFn) {
   });
 }
 
+export function lineNumberAt(text, index) {
+  let line = 1;
+  for (let offset = 0; offset < index && offset < text.length; offset++) {
+    if (text[offset] === "\n") line++;
+  }
+  return line;
+}
+
 export function safeRead(path) {
   try {
     const st = statSync(path);

package/docs/releases/v0.2.14.md

@@ -1,93 +0,0 @@
-# Weavatrix 0.2.14
-
-0.2.14 is a trust and maintainability release found by dogfooding the MCP on a Go BGP service and a
-Java event-driven application. It keeps the 38-tool surface and the local-first/Hosted wire boundary,
-while closing false dead-code, false clean-health, noisy flow, weak architecture-bootstrap, and stale
-daemon failure modes.
-
-## Go receiver-aware call flow
-
-- Go call resolution now carries receiver types from function parameters, explicit and inferred
-  locals, constructor return types (including the first value of `value, err := pkg.New()`), imported
-  package types, and struct fields.
-- Calls such as `bgpSpeaker.RemoveMitigator(update)` resolve to
-  `(*Speaker).RemoveMitigator` instead of leaving the method falsely test-only.
-- Unknown or ambiguous same-name receivers still fail closed rather than inventing a call edge.
-
-## Focused generic flows
-
-- `query_graph` accepts exact `seed_symbols`, a `relation_filter`, and
-  `flow_direction: forward|backward|both`. The same bounded graph can now trace Kafka listeners,
-  queues, workers, cron jobs, CLI entry points, and other event/data flows without one tool per
-  framework.
-- Exact seeds remain exclusive unless `augment_seeds:true` is requested. CamelCase identifiers such
-  as `FlowSpec` no longer opt tests into production traversal merely because they contain `spec`.
-- `context_bundle` ranks production callers before classified test callers and uses diverse,
-  non-overlapping excerpts around decisive call sites.
-
-## Honest Health and endpoint state
-
-- `run_audit` returns an explicit capability matrix for structure, dependencies, runtime correctness,
-  concurrency, advisories, malware scanning, and measured coverage. Each row has independent status
-  and completeness.
-- Maven and Gradle manifests are detected and inventoried, but unsupported import-to-artifact
-  verification returns `NOT_SUPPORTED`/`PARTIAL` instead of a misleading complete zero.
-- Conservative source checks can flag selected Go fixed-index slice/discriminator hazards and Java
-  interruption/retry candidates, including conditional `while` and `do/while` loops with failure plus
-  wait behavior but no visible attempt/deadline/cancellation policy. The result explicitly does not
-  claim compiler, runtime, CFG, race, or full concurrency proof.
-- Ordinary Go grouped imports (`import (...)`) no longer trigger the JavaScript dynamic-import caveat;
-  real Go reflection evidence remains visible independently.
-- Spring endpoint inventory includes conditional activation evidence and whether a controller is
-  inactive by default.
-
-## Safe target-architecture bootstrap
-
-- The starter discovers adaptive Maven/Gradle source roots and nested monorepo product territories
-  instead of grouping an entire Java application under its first directory. Oversized Java package
-  branches split recursively at real child packages, while a large flat package remains an honest
-  size hotspot instead of being divided into invented components.
-- Observed dependency directions are proposed separately as `OBSERVED_NOT_ENFORCED`; inventory is not
-  silently promoted to intended architecture.
-- Only universal starter guards (`runtimeCycles=0`, `maxFileLoc=300`) are active. Generic function,
-  complexity, cohesion, and boundary thresholds are returned as `CANDIDATE_NOT_ENFORCED` so a first
-  preview does not manufacture hundreds of policy violations.
-- `maxFileLoc` now reads physical file LOC stored on file nodes, not the last declaration's end line;
-  older graphs rebuild before this budget can report a pass.
-- `get_architecture_contract action=preview` returns the materialized candidate, verification, exact
-  file content/hash, and a short-lived token without writing. `action=approve` rechecks repository and
-  graph identity, then creates only a missing `.weavatrix/architecture.json` with the exact reviewed
-  content. Existing policy is never overwritten.
-- `baseline_mode=accept-current` is an explicit owner action for ratcheting accepted current debt; the
-  default records no baseline findings.
-
-## Runtime and codebase integrity
-
-- The MCP compares its running version with the package version on disk. A mismatch blocks
-  `initialize`, `tools/list`, and tool calls with `STALE_RUNTIME` until the client reconnects. The
-  environment override is reserved for deliberate source development.
-- Large MCP, graph, analysis, precision, and test modules were split into owner-focused folders with
-  stable hot-reload facades. The watcher and cache-busting chain include the new graph, Health,
-  action, and architecture owner modules, so supported tool edits still go live without reconnecting.
-- The public page keeps the same design and continuous canvas graph animation while CSS and animation
-  code move into focused assets. A release test enforces a physical 300-line ceiling for
-  JavaScript/TypeScript under `src`, `bin`, `scripts`, and `test`, plus site HTML/CSS/JavaScript.
-- The 38-tool catalog and profile counts remain unchanged: 31 pinned, 34 offline, 35 OSV, and 38
-  hosted/full.
-
-## Compatibility and security
-
-- Hosted payload v2/v3, `preview_sync` confirmation, and architecture-contract transport are
-  unchanged. This release does not modify the separate Hosted frontend/backend application.
-- Local architecture approval writes only inside the active repository boundary, uses an exclusive
-  create, expires and consumes tokens, rejects repository/graph drift, and refuses an existing target.
-- Source bodies, snippets, absolute paths, credentials, environment values, and Git remotes remain
-  excluded from Hosted sync payloads.
-
-## Verification
-
-The release is gated by the full Node suite (538 tests: 535 passed and three platform skips), the
-six-language fixture benchmark, a 6/6 real-repository semantic-regression gate, zero npm audit
-vulnerabilities, packed npm and MCPB stdio checks, plus direct Go and Java dogfooding. Cold timings
-vary with machine load and repository snapshots; the public README keeps a dated representative
-run instead of presenting one release machine's timing as a universal result.