morluto/rea
1
0
Fork 0
mirror of https://github.com/morluto/rea.git synced 2026-11-05 06:45:22 +00:00
Code Issues 1.3k Projects Packages Wiki Activity

[PR #6318] [CLOSED] fix(deps): pin vite to 8.3.5 so npm audit stops reporting the launch-editor advisories #7279

New issue
Closed
opened 2026-11-01 21:46:42 +00:00 by bsakaguchi · 0 comments
bsakaguchi commented 2026-11-01 21:46:42 +00:00
Owner
Copy link

📋 Pull Request Information

Original PR: https://github.com/morluto/rea/pull/6318
Author: @DarkNio88
Created: 10/22/2026
Status: ❌ Closed

Base: main ← Head: fix/vite-8.3.5-advisory

📝 Commits (1)

  • 58f81b0 fix(deps): pin vite to 8.3.5 so npm audit stops reporting the launch-editor advisories

📊 Changes

2 files changed (+371 additions, -6 deletions)

View changed files

📝 package-lock.json (+370 -6)
📝 package.json (+1 -0)

📄 Description

Summary

vite is now pinned to 8.3.5 through a top-level npm override, and the lockfile is refreshed accordingly. npm audit reports 0 vulnerabilities on this branch, against one high-severity finding for vite on the base revision.

Problem and expected behavior

npm audit reports one high-severity advisory for vite on the base revision: node node_modules/vite, range 8.3.0 - 8.3.2, with six advisories in total (GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pm, GHSA-9jrq-w75r-8gcw, GHSA-rq7h-c2jc-7f22, GHSA-vfpm-58rq-9qcg). They cover the launch-editor handling on Windows and the Vite dev server.

Observed facts, all measured on the base revision:

  • The committed lockfile resolves node_modules/vite to 8.3.2, which is inside the affected range 8.3.0 - 8.3.2, so the finding applies to the tree as it is committed. This was read directly from package-lock.json at the base revision (git show origin/main:package-lock.json).
  • The registry advisory endpoint POST /-/npm/v1/security/advisories/bulk returns no advisory for vite@8.3.5 and six advisories for vite@8.3.0.
  • vite is a dev-only transitive dependency of vitest@5.0.3, so it never reaches a published artifact, and the dev server it powers is not exposed by REA.

Change and scope

  • package.json: add the top-level overrides.vite = "8.3.5", so the vitest -> vite edge resolves to exactly 8.3.5 and cannot fall back into the affected range.
  • package-lock.json: refresh the vite subtree. node_modules/vite moves from 8.3.2 to 8.3.5, and 18 nested entries are added under node_modules/vite/node_modules/ for vite's own dependencies (rolldown 1.2.15 with its platform bindings, postcss 8.5.31, @oxc-project/types 0.155.0). No package is removed.
  • The pre-existing nested override overrides.vitepress.vite = "6.4.4" is untouched: vitepress 1.6.4 requires its own vite 6.4.4, so the documentation build keeps the version it pins today.
  • Not included: no runtime dependency change, no change to the published package, no upgrade beyond the vite subtree.

Contract and boundary impact

  • Semantic owner and earliest changed stage: npm dependency resolution for the dev-only test runner; the earliest changed stage is package.json and package-lock.json.
  • Contribution scope fit and linked maintainer decision: ordinary dependency fix inside existing boundaries; not applicable for a maintainer scope decision, since no provider, target execution, injection, mutation, or protection recovery is involved.
  • CLI and MCP/tool-catalog contract: none.
  • Provider, bridge, target-format, or platform compatibility: none. vite is a dev-only transitive dependency of vitest 5.0.3 and never reaches a published artifact.
  • Evidence, artifact, provenance, or reconstruction contract: none.
  • Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable.
  • Generated metadata (docs/public/product-catalog.json), package, or installation impact: none. docs/public/product-catalog.json and skills/ are ignored outputs and are not modified here.

Expected effects: none of the listed effects apply to target interaction. The change only constrains dev-time dependency resolution of a test-runner dependency; no target is read, launched, instrumented, or modified, and REA's runtime behavior is unchanged.

Evidence and regression coverage

  • Tests added or updated: none. The change does not alter product behavior.
  • Base reproduction or other evidence: in a pristine checkout of the base revision without node_modules, npm audit reports one high-severity finding for node_modules/vite (range 8.3.0 - 8.3.2); the same checkout with this override reports 0 vulnerabilities. The registry endpoint POST /-/npm/v1/security/advisories/bulk answers with no advisory for vite@8.3.5 and six advisories for vite@8.3.0.
  • User-visible CLI/MCP output (if applicable): none.
  • Remaining proof gaps: the audit finding was reproduced on Windows only; the behavior on Linux and macOS was not verified. The comparison used lockfile-only audits (no npm ci), because the local Node 25.9.0 aborts npm ci on the repository engines range. The focused Hopper test cannot run in a fresh checkout on this Windows host, because the packaged native Windows artifact is missing; it fails the same way on the base revision.

For evidence-bearing changes:

  • Observed, derived, and inferred claims remain distinguishable.
  • Artifact identity, source provenance, and failed attempts remain preserved.
  • Unsupported, incomplete, unavailable, or uncertain outcomes remain visible.

Validation performed

  • npm audit on a pristine checkout of the base revision (git worktree add --detach <tmp> origin/main, no node_modules, Node 24.18.0 / npm 11.16.0) - 1 high-severity finding for node_modules/vite, range 8.3.0 - 8.3.2, with the six advisories listed above; the lockfile there resolves node_modules/vite to 8.3.2.
  • npm audit on this branch (same worktree procedure, Node 24.18.0 / npm 11.16.0) - 0 vulnerabilities ({"info":0,"low":0,"moderate":0,"high":0,"critical":0,"total":0}).
  • npm install --ignore-scripts (Node 24.18.0, npm 11.16.0) - exit 0; the committed package-lock.json is left unchanged by the install, so the resolved tree in the lockfile is stable.
  • npm ls vite --all - vitest@5.0.3 -> vite@8.3.5 (overridden); vitepress@1.6.4 -> vite@6.4.4 (overridden).
  • npm run check:fast - exit 0 (turbo: typecheck and lint, 2/2 tasks successful).
  • npm run test:focused -- tests/composition/callPathParserOperation.test.ts tests/composition/evmModuleContract.test.ts - exit 0 (2 test files, 3 tests passed).
  • npm run test:focused -- tests/boundary/providers/hopper/hopperArguments.test.ts - exit 1 on this Windows host, in the test bootstrap and before any assertion: "REA Windows native controls are unavailable: Missing packaged Windows native file native/windows/build/manifest.json (ENOENT)". The same command, with the same install procedure in a fresh checkout of the base revision, fails with the identical message, so the failure is pre-existing and comes from the missing packaged native Windows artifact, not from the dependency resolution changed here.
  • POST https://registry.npmjs.org/-/npm/v1/security/advisories/bulk with {"vite":["8.3.5"]} - no advisory; with {"vite":["8.3.0"]} - six advisories.
  • Lockfile comparison between the base revision and this branch - node_modules/vite moves from 8.3.2 to 8.3.5, 18 entries are added under node_modules/vite/node_modules/ (rolldown 1.2.15 with its platform bindings, postcss 8.5.31, @oxc-project/types 0.155.0), no package is removed.

Compatibility, safety, and release

  • Breaking changes or migration steps: none.
  • Real Hopper/Ghidra, browser, or OS coverage: not applicable; dependency resolution only.
  • Package or release metadata impact: none. The published package does not contain vite.
  • Security, privacy, process, or containment review: removes a reported advisory finding from npm audit output. No runtime permission, network, or process behavior changes.

Author readiness

Human owner: @DarkNio88

  • I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work.
  • I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps.
  • I declare this PR ready for initial maintainer review.

Before merge

  • This PR addresses a concrete problem or an agreed enhancement.
  • Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff.
  • The PR has one focused outcome and the title follows type(scope): outcome.
  • Related issue is linked, or the reason for not linking one is stated above.
  • Tests cover changed observable behavior and meaningful failure paths.
  • Owning docs, contracts, and generated metadata are updated where needed.
  • User-visible CLI/MCP changes include representative output.
  • I checked the final diff for secrets, unrelated cleanup, and unsupported claims.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/morluto/rea/pull/6318 **Author:** [@DarkNio88](https://github.com/DarkNio88) **Created:** 10/22/2026 **Status:** ❌ Closed **Base:** `main` ← **Head:** `fix/vite-8.3.5-advisory` --- ### 📝 Commits (1) - [`58f81b0`](https://github.com/morluto/rea/commit/58f81b0d69141a336ccf969be971a4cad55b7c06) fix(deps): pin vite to 8.3.5 so npm audit stops reporting the launch-editor advisories ### 📊 Changes **2 files changed** (+371 additions, -6 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+370 -6) 📝 `package.json` (+1 -0) </details> ### 📄 Description ## Summary `vite` is now pinned to 8.3.5 through a top-level npm override, and the lockfile is refreshed accordingly. `npm audit` reports 0 vulnerabilities on this branch, against one high-severity finding for `vite` on the base revision. ## Problem and expected behavior `npm audit` reports one high-severity advisory for `vite` on the base revision: node `node_modules/vite`, range `8.3.0 - 8.3.2`, with six advisories in total (GHSA-698v-4r3x-3vcv, GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pm, GHSA-9jrq-w75r-8gcw, GHSA-rq7h-c2jc-7f22, GHSA-vfpm-58rq-9qcg). They cover the `launch-editor` handling on Windows and the Vite dev server. Observed facts, all measured on the base revision: - The committed lockfile resolves `node_modules/vite` to 8.3.2, which is inside the affected range `8.3.0 - 8.3.2`, so the finding applies to the tree as it is committed. This was read directly from `package-lock.json` at the base revision (`git show origin/main:package-lock.json`). - The registry advisory endpoint `POST /-/npm/v1/security/advisories/bulk` returns no advisory for `vite@8.3.5` and six advisories for `vite@8.3.0`. - `vite` is a dev-only transitive dependency of `vitest@5.0.3`, so it never reaches a published artifact, and the dev server it powers is not exposed by REA. ## Change and scope - `package.json`: add the top-level `overrides.vite = "8.3.5"`, so the `vitest` -> `vite` edge resolves to exactly 8.3.5 and cannot fall back into the affected range. - `package-lock.json`: refresh the `vite` subtree. `node_modules/vite` moves from 8.3.2 to 8.3.5, and 18 nested entries are added under `node_modules/vite/node_modules/` for vite's own dependencies (`rolldown` 1.2.15 with its platform bindings, `postcss` 8.5.31, `@oxc-project/types` 0.155.0). No package is removed. - The pre-existing nested override `overrides.vitepress.vite = "6.4.4"` is untouched: vitepress 1.6.4 requires its own vite 6.4.4, so the documentation build keeps the version it pins today. - Not included: no runtime dependency change, no change to the published package, no upgrade beyond the `vite` subtree. ## Contract and boundary impact - Semantic owner and earliest changed stage: npm dependency resolution for the dev-only test runner; the earliest changed stage is `package.json` and `package-lock.json`. - Contribution scope fit and linked maintainer decision: ordinary dependency fix inside existing boundaries; not applicable for a maintainer scope decision, since no provider, target execution, injection, mutation, or protection recovery is involved. - CLI and MCP/tool-catalog contract: none. - Provider, bridge, target-format, or platform compatibility: none. `vite` is a dev-only transitive dependency of vitest 5.0.3 and never reaches a published artifact. - Evidence, artifact, provenance, or reconstruction contract: none. - Target selection, authority, upstream behavior, and cleanup details (if applicable): not applicable. - Generated metadata (`docs/public/product-catalog.json`), package, or installation impact: none. `docs/public/product-catalog.json` and `skills/` are ignored outputs and are not modified here. Expected effects: none of the listed effects apply to target interaction. The change only constrains dev-time dependency resolution of a test-runner dependency; no target is read, launched, instrumented, or modified, and REA's runtime behavior is unchanged. ## Evidence and regression coverage - Tests added or updated: none. The change does not alter product behavior. - Base reproduction or other evidence: in a pristine checkout of the base revision without `node_modules`, `npm audit` reports one high-severity finding for `node_modules/vite` (range `8.3.0 - 8.3.2`); the same checkout with this override reports 0 vulnerabilities. The registry endpoint `POST /-/npm/v1/security/advisories/bulk` answers with no advisory for `vite@8.3.5` and six advisories for `vite@8.3.0`. - User-visible CLI/MCP output (if applicable): none. - Remaining proof gaps: the audit finding was reproduced on Windows only; the behavior on Linux and macOS was not verified. The comparison used lockfile-only audits (no `npm ci`), because the local Node 25.9.0 aborts `npm ci` on the repository `engines` range. The focused Hopper test cannot run in a fresh checkout on this Windows host, because the packaged native Windows artifact is missing; it fails the same way on the base revision. For evidence-bearing changes: - [x] Observed, derived, and inferred claims remain distinguishable. - [x] Artifact identity, source provenance, and failed attempts remain preserved. - [x] Unsupported, incomplete, unavailable, or uncertain outcomes remain visible. ## Validation performed - `npm audit` on a pristine checkout of the base revision (`git worktree add --detach <tmp> origin/main`, no `node_modules`, Node 24.18.0 / npm 11.16.0) - 1 high-severity finding for `node_modules/vite`, range `8.3.0 - 8.3.2`, with the six advisories listed above; the lockfile there resolves `node_modules/vite` to 8.3.2. - `npm audit` on this branch (same worktree procedure, Node 24.18.0 / npm 11.16.0) - 0 vulnerabilities (`{"info":0,"low":0,"moderate":0,"high":0,"critical":0,"total":0}`). - `npm install --ignore-scripts` (Node 24.18.0, npm 11.16.0) - exit 0; the committed `package-lock.json` is left unchanged by the install, so the resolved tree in the lockfile is stable. - `npm ls vite --all` - `vitest@5.0.3` -> `vite@8.3.5` (overridden); `vitepress@1.6.4` -> `vite@6.4.4` (overridden). - `npm run check:fast` - exit 0 (turbo: typecheck and lint, 2/2 tasks successful). - `npm run test:focused -- tests/composition/callPathParserOperation.test.ts tests/composition/evmModuleContract.test.ts` - exit 0 (2 test files, 3 tests passed). - `npm run test:focused -- tests/boundary/providers/hopper/hopperArguments.test.ts` - exit 1 on this Windows host, in the test bootstrap and before any assertion: "REA Windows native controls are unavailable: Missing packaged Windows native file native/windows/build/manifest.json (ENOENT)". The same command, with the same install procedure in a fresh checkout of the base revision, fails with the identical message, so the failure is pre-existing and comes from the missing packaged native Windows artifact, not from the dependency resolution changed here. - `POST https://registry.npmjs.org/-/npm/v1/security/advisories/bulk` with `{"vite":["8.3.5"]}` - no advisory; with `{"vite":["8.3.0"]}` - six advisories. - Lockfile comparison between the base revision and this branch - `node_modules/vite` moves from 8.3.2 to 8.3.5, 18 entries are added under `node_modules/vite/node_modules/` (`rolldown` 1.2.15 with its platform bindings, `postcss` 8.5.31, `@oxc-project/types` 0.155.0), no package is removed. ## Compatibility, safety, and release - Breaking changes or migration steps: none. - Real Hopper/Ghidra, browser, or OS coverage: not applicable; dependency resolution only. - Package or release metadata impact: none. The published package does not contain `vite`. - Security, privacy, process, or containment review: removes a reported advisory finding from `npm audit` output. No runtime permission, network, or process behavior changes. ## Author readiness Human owner: @DarkNio88 - [ ] I reviewed the final diff and relevant existing code, understand the change and its edge cases, and take responsibility for the complete PR, including AI-assisted work. - [ ] I checked the evidence above, confirmed it supports the current change, and recorded meaningful validation gaps. - [ ] I declare this PR ready for initial maintainer review. ## Before merge - [ ] This PR addresses a concrete problem or an agreed enhancement. - [ ] Material scope and authority questions are resolved, and any required maintainer scope decision covers the final diff. - [ ] The PR has one focused outcome and the title follows `type(scope): outcome`. - [ ] Related issue is linked, or the reason for not linking one is stated above. - [ ] Tests cover changed observable behavior and meaningful failure paths. - [ ] Owning docs, contracts, and generated metadata are updated where needed. - [ ] User-visible CLI/MCP changes include representative output. - [ ] I checked the final diff for secrets, unrelated cleanup, and unsupported claims. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
bsakaguchi 2026-11-01 21:46:42 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
codex/procedure-reference-stacked
release-please--branches--main--components--rea-agents
release-please--branches--main--components--rea-agents--release-notes
codex/kuna-independent-retry
codex/byte-search-overlay-coverage
codex/open-failure-target-receipt
codex/kuna-xref-evidence
codex/ghidra-ambiguous-procedure-recovery
codex/function-source-bundle
codex/trace-function-integration-prototype
codex/snapshot-source-closure
codex/recorded-evidence-array-pages
codex/evidence-recovery-redesign
codex/trace-feature-address-scope
codex/call-discovery-scope
codex/ghidra-literal-candidate-evidence
codex/decompile-directory-independent-retry
codex/retry-provenance-base
codex/value-flow-capability-experiment
codex/ghidra-containing-instruction
cursor/readme-discord-button-ef9f
dependabot/github_actions/actions/setup-node-7.1.0
dependabot/github_actions/actions/upload-artifact-7.0.2
dependabot/npm_and_yarn/npm-minor-and-patch-d8d97ce6df
codex/kuna-1989
fix/8559-native-ui-fixture-ownership
fix/8555-go-verifier-mcp-ownership
codex/provider-capability-recovery
fix/8642-rizin-target-stdin
codex/ghidra-memory-effect-scope
codex/ghidra-annotation-entry-selector
codex/ghidra-readonly-recovery
codex/ghidra-regex-verifier-recovery
codex/evidence-discovery-view-guidance
fix/8545-bulk-append-overflow
fix/8428-navigation-refusal-alternatives
codex/address-context-recovery
codex/matching-member-limitations
codex/unknown-scope-contract
codex/evidence-view-guidance
feat/8373-native-trace-views
codex/ghidra-snapshot-verifier-binding
codex/elf-export-visibility
codex/evidence-view-recovery
codex/native-reference-cli-help
codex/provider-candidate-observation-scope
codex/kuna-session-verification
codex/ghidra-switch-lifetime-guidance
codex/pseudocode-paging-discovery
codex/clarify-evidence-view-support
codex/kuna-xrefs-selector-recovery
codex/context-capacity-recovery
codex/evidence-closure-large-links
codex/same-function-evidence-identity
codex/ghidra-verifier-inspected-jdk
codex/audit-guided-workflows
codex/crash-prompt-retained-dossiers
codex/analysis-view-error-recovery
codex/kuna-verifier-target-selection
codex/ghidra-selected-project-call-coverage
codex/docs-native-analysis-scope
codex/ghidra-java-socket-boundary
codex/ghidra-retained-snapshot-verifier
codex/ghidra-search-inventory-facts
fix/8284-zero-argument-parameter-bindings
fix/8198-ui-action-handler-offset
fix/8257-elf-entry-label-identity
fix/8304-deferred-output-schema-projection
fix/8277-call-path-computed-target-uncertainty
fix/pr-8089-conflicts
fix/ci-static-duplicate-export
dependabot/npm_and_yarn/lint-staged-17.6.0
dependabot/github_actions/actions/download-artifact-8.0.2
dependabot/npm_and_yarn/write-file-atomic-8.0.0
dependabot/npm_and_yarn/canonicalize-5.1.0
dependabot/github_actions/actions/cache/restore-6.1.0
dependabot/npm_and_yarn/toon-format/toon-4.4.0
dependabot/github_actions/actions/deploy-pages-5.0.1
codex/review-fixes-pr-2403
codex/review-fixes-pr-2400
codex/process-terminal-width
codex/test-brittleness-cleanup
verify/7167-browser-connect-macos
fix/7167-browser-connect
feat/native-matching-allowance-setting
feat/browser-scenario-dry-run
test/managed-caller-parameters-20261024
codex/parser-fortythird-boundaries
fix/6926-pinvoke-platform-decorations-20261023
fix/6889-har-body-encoding-20261023
fix/6888-sqlite-schema-budget-20261023
fix/dependency-security-gates-6708
cursor/evidence-overwrite-rebase-b4ac
feat/4057-verify-native-exports
fix/windows-acl-observer-overhead-20261022
cursor/erlang-beam-restack-4476
cursor/pe-certificate-review-bf32
fix/6116-javascript-application-fs-errors
fix/6061-unmapped-runtime-script-unknown
feat/browser-scenario-summary
fix/pe-certificates
codex/verify-3407
cursor/rebase-5699
cursor/rebase-5352
cursor/rebase-5600
cursor/fix-cli-schema-omission-10a8
codex/audit-hopper-shutdown-reasons-20261021
fix/demangle-swift-omitted-record
fix/nib-boolean-value-types
cursor/cancellation-partial-observation-a5ac
fix/ib-object-limit-reasons
fix/electron-fuse-limit-advice
fix/kuna-doctor-dangling-cache
fix/fixed-budget-refusal-advice
fix/js-ipc-listener-dedup
fix/js-return-member-provenance
fix/dmg-integrity-retry-advice
fix/ida-doctor-readiness
fix/kuna-version-probe-output-drain
fix/legacy-swift-runtime-name-matching
fix/dylib-lazy-load-commands
fix/browser-scenario-startup-cancel
fix/swift-nested-punycode-classification
fix/compare-unselected-scopes
fix/objc-method-budget-coverage
fix/dmg-mounted-root-observations
audit/ci-tests-20261019-round2
release/6.7.0
fix/wabt-cleanup-retry-resolution
fix/electron-fuse-elf-pe-architecture
fix/native-plist-descriptor-ownership
fix/kuna-caller-cleanup-ownership
experiment/atomic-codemode-20261016
review/first-contributor-3776
fix/call-resolution-full-read-cycles
fix/member-mutation-selection-repeat
experiment/atomic-re-tools-20261015
perf/member-mutation-lazy-origins
perf/static-network-mutation-index
fix/hopper-startup-lifecycle
audit/3050-windows-proof-20261015
feat/windows-window-capture-2183
audit/3049-windows-proof-20261015
audit/3735-macos-fixtures-20261015
fix/batch-decompile-null-pseudocode
fix/kuna-inventory-honors-jobs
experiment/browser-codemode-tool-design-20261015
fix/hopper-clean-runtime-argv
codex/review-2049-27f1b367
review-fixes/pr-2787-routing
fix/3360-scoped-this-emitters
fix/3367-replaced-global-effects
fix/3838-compact-any-value-items
test/hopper-download-probe-20261015
codex/windows-runtime-creation-red-green-20261015
codex/windows-readonly-root-red-green-20261015
codex/windows-root-share-red-green-20261015
codex/exp-1685-win-mcp-startup
codex/bug-sweep-20261015
investigate/2190-windows-package-phases
investigate/3543-macos-cli-deadline
perf/3281-reverse-tools-feedback-quality
fix/3406-hopper-doctor-fixture
fix/3341-wrapper-require-test-context
fix/3301-owned-uninstall-fixtures
fix/3164-compiler-input-ownership
fix/pcap-cleanup-stdout-newline-20261014
perf/interface-builder-summary
codex/review-fixes-pr-1977
fix/ghidra-effective-jvm-platform
fix/docs-turkish-rust-link-20261013
fix/main-maintenance-ci-20261010
fix/recover-binary-session-process-effects
codex/review-fixes-pr-2457
codex/ci-required-cancellation-gate
fix/main-format-baseline-20261013
fix/setup-preserve-entry-fields
cursor/restore-main-checks-1ffc
fix/ghidra-bridge-hashmap-import
codex/shared-ci-jadx-json-default-20261013
codex/shared-ci-ghidra-test-groups-20261013
codex/shared-ci-java-fixture-format-20261013
codex/fix-intrinsic-invocation-boundaries
test/release-preflight-reusable-jobs
test/js-parameter-provenance-expectation
fix/linux-hopper-verification-current
test/2419-ghidra-elf-probe-size
followup/pr-1544-native-ida
codex/fold-pr-2230-contribution
docs/readme-responsible-use
fix/issue-2064
fix/issue-2050
fix/issue-2053
fix/issue-1968
fix/issue-1945
experiment/codemode-bridge-20261011
fix/tool-effects-negative-wording-1904-20261012
fix/1842-electron-interop-provenance
feat/recover-javascript-multi-input
refactor/website-i18n-prep
fix/nativeaot-pe-virtual-extent
fix/browser-verifier-ci-hang
fix/pe-resources-input-selection
docs/beginner-friendly-guides
docs/beginner-setup-guide
fix/javascript-analysis-worker-1563
fix/1649-ghidra-duplicate-names
fix/javascript-export-keys-integration-1369
test/maintenance-boundary-contracts-20261011
review/javascript-export-keys-1369
review/process-live-progress-1483
test/javascript-1495-growth-ratio
fix/ci-escape-timing
docs/normalized-terminal-geometry-1450
release/6.3.0
archive/release-6.3.0-pr1381
release/6.2.0
fix/electron-preload-dynamic-override
fix/javascript-self-referential-bundler-edges
release/6.1.0
cursor/grok-client-cherry-pick-0b56
feat/signature-posture
feat/dyld-shared-cache
feat/artifact-integrity-policy
feat/pkg-inventory
release/6.0.0
chore/sync-release-5.0.0
release/5.0.0
cursor/cloud-agent-node-787e
fix/javascript-xhr-open-endpoints
review/pr-711-realpath-fallback-wording
cleanup/replay-confinement
codex/test-suite-performance
codex/issue-foundations
codex/address-open-issues-2026-07-20
agent/javascript-vite-rollup-esbuild-adapters
agent/process-cleanup
agent/triage-integration
agent/unknown-commands-registry
feat/mcp-identity-metadata
morlvps/issue_cleanup
codex/installer-redesign
morl/roadmap-investigation-core
morl/roadmap-investigation-docs
release-please--branches--main--components--rea
rea-agents-6.8.0
rea-agents-6.7.0
rea-agents-6.6.0
experiment/atomic-codemode-wait-runtime-20261016
rea-agents-6.5.0
rea-agents-6.4.0
rea-agents-6.3.0
rea-agents-6.2.0
rea-agents-6.1.0
rea-agents-6.0.0
rea-agents-5.0.0
rea-agents-4.1.0
rea-agents-4.0.1
rea-agents-4.0.0
rea-agents-3.2.1
rea-agents-3.2.0
rea-agents-3.1.0
rea-agents-3.0.0
rea-agents-2.7.0
rea-agents-2.6.0
rea-agents-2.5.1
rea-agents-2.5.0
rea-agents-2.4.0
rea-agents-2.3.0
rea-agents-2.2.0
rea-agents-2.1.0
rea-agents-2.0.0
rea-agents-1.7.0
rea-agents-1.6.0
rea-agents-1.5.0
rea-agents-1.4.0
rea-agents-1.3.0
rea-agents-1.2.0
rea-agents-1.1.0
rea-agents-1.0.0
rea-agents-0.5.0
rea-agents-0.4.0
rea-agents-0.3.0
rea-0.2.1
rea-0.2.0
Labels
Clear labels   
area: bridge

   
area: bridge

   
area: build

   
area: build

   
area: build

   
area: cli

   
area: domain

   
area: evidence

   
area: mcp

   
area: native

   
area: providers

   
area: runtime

   
area: server

   
area: setup

   
area: tests

   
bug

   
design

   
documentation

   
enhancement

   
enhancement

   
enhancement

   
experiment

   
help wanted

   
i18n

   
invalid

   
P0: critical

   
P1: high

   
P2: medium

   
P2: medium

   
P2: medium

   
P3: low

   
performance

   
provider-request

   
pull-request
Mirrored from GitHub Pull Request

  
question

   
roadmap

   
triage
No labels
area: bridge
area: bridge
area: build
area: build
area: build
area: cli
area: domain
area: evidence
area: mcp
area: native
area: providers
area: runtime
area: server
area: setup
area: tests
bug
design
documentation
enhancement
enhancement
enhancement
experiment
help wanted
i18n
invalid
P0: critical
P1: high
P2: medium
P2: medium
P2: medium
P3: low
performance
provider-request
pull-request
question
roadmap
triage
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
morluto/rea#7279
No description provided.