fix(security): eliminate Rust and npm dependency advisories - #739
Merged
Conversation
ruvnet
force-pushed
the
agent/security-advisory-wave
branch
from
July 28, 2026 04:06
cc81a7f to
a763cf7
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
wee_alloc, upgrade pprof/tract/prometheus and other security-sensitive dependencies@ruvector/spiking-neural1.0.3@ruvector/agentic-synth0.1.7@ruvector/burst-scaling1.0.2ruvbot0.3.3distartifact is actually includedSecurity validation
cargo auditacross 50 committed lockfiles: 0 actionable vulnerabilitiesnpm install --package-lock-onlywith no existing node_modules: 0 vulnerabilitiesnpm ci --ignore-scripts --force: passnpm audit --audit-level=low: 0 vulnerabilitiesBuild validation
cargo fmt --all -- --checkcargo check --manifest-path examples/data/Cargo.toml --workspacegit diff --checkNotes
The GunDB feature name remains accepted for compatibility, but now uses the maintained local transport. This avoids shipping the vulnerable ring/tungstenite/nix stack from the unmaintained backend.
RuVocal's existing Svelte diagnostics remain at the main-branch baseline (186 errors); this change introduces no new diagnostics.
Closes #736