🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
TypeScript agentic-aiagentic-frameworkagentic-workflowagentsai-agentsai-assistantai-skillsautonomous-agentsclaudecodexdsh-pluginharnessmcp-servermulti-agentmulti-agent-systemsnpmskillsswarmswarm-intelligencetypescript
fix(supply-chain): correct tracking issue ref in vitest accepted-finding (#2270 was a typo for #2268)
ruv920ba4b04ed1
diff --git a/.github/supply-chain/accepted-findings.json b/.github/supply-chain/accepted-findings.jsonindex 5058bfc705..19c825e4be 100644--- a/.github/supply-chain/accepted-findings.json+++ b/.github/supply-chain/accepted-findings.json@@ -35,8 +35,8 @@"depName": "vitest","severity": "critical","via": ["GHSA-5xrq-8626-4rwp"],- "tracking": "ruflo#2270 — Vitest <4.1.0 UI server arbitrary-file-read/exec (CWE-862, CVSS 9.8). vitest is a devDependency only — never in the published tarball, never in the runtime path. The advisory's exploit requires the Vitest UI server (vitest --ui) to be listening, which only happens during interactive local test development. CI (--run) and production install (--omit=dev) never activate the UI server. Spec was already bumped to ^4.1.0 in v3/@claude-flow/browser/package.json on 2026-06-02 (release/3.10.34); the standalone-publish package-lock.json carries workspace:* refs that npm cannot resolve in isolation, so the lockfile refresh has to wait until the next workspace-coordinated rebuild. Tracked separately so this entry expires the moment that rebuild lands.",- "trackingIssue": "https://github.com/ruvnet/ruflo/issues/2270",+ "tracking": "ruflo#2268 — Vitest <4.1.0 UI server arbitrary-file-read/exec (CWE-862, CVSS 9.8). vitest is a devDependency only — never in the published tarball, never in the runtime path. The advisory's exploit requires the Vitest UI server (vitest --ui) to be listening, which only happens during interactive local test development. CI (--run) and production install (--omit=dev) never activate the UI server. Spec was already bumped to ^4.1.0 in v3/@claude-flow/browser/package.json on 2026-06-02 (release/3.10.34); the standalone-publish package-lock.json carries workspace:* refs that npm cannot resolve in isolation, so the lockfile refresh has to wait until the next workspace-coordinated rebuild. Tracked separately so this entry expires the moment that rebuild lands.",+ "trackingIssue": "https://github.com/ruvnet/ruflo/issues/2268","expiresAt": "2026-09-02","rationale": "devDependency-only + exploit requires `vitest --ui` which is local-dev only. Spec already requires ^4.1.0; only the standalone package-lock graph hasn't refreshed (workspace:* protocol limitation on raw `npm install`). Zero production / CI exposure. Re-audit and remove this entry the next time the browser's package-lock.json is regenerated."}