MystenLabs/walrus

Public scan — anyone with this URL can view this analysis. Sign up to track your own repos privately, run scheduled re-scans, and get AI fix prompts via your dashboard.

108 of your 316 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 2.8s · analysis 37.32s · 15.1 MB · GitHub API rate-limit (preflight)

https://github.com/MystenLabs/walrus · scanned 2026-06-06 00:55 UTC (4 days, 1 hour ago) · 10 languages

545 raw signals (275 security + 270 graph) 5th percentile · Rust · large (100-500K LoC) System graph score 61 (lower by 8)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 1 hour ago · v2 · 260 actionable findings from 2 signal sources. 125 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

100.0% cov · 116 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	60.0	0.15	9.00
`security_score`	9.6	0.25	2.40
`testing_score`	35.0	0.20	7.00
`documentation_score`	98.0	0.15	14.70
`practices_score`	94.0	0.15	14.10
`code_quality`	53.5	0.10	5.35
Overall		1.00	52.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 4 High 55 Medium 65 Low 98 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 144 System graph 116 Crowd 0 Layer: Security 20 Software 116 Cicd 14 Quality 71 Api 1 Frontend 24 Network 3 Hardware 11

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Duplicates & near-duplicates 1 finding

What it is: Same function copy-pasted into multiple modules with minor variations.

Why it matters: Each copy drifts independently — bug fixes apply to one, miss the others.

How AI causes it: AI completes the same pattern in each file rather than refactoring to a shared helper.

Fix approach: Extract the duplicated logic into the most general module both call sites already import. Add tests at the helper level.

1 matching finding on this repo

low Near-duplicate function bodies in 2 places

View all duplicates & near-duplicates findings →

Legacy markers 1 finding

What it is: TODO, FIXME, XXX, HACK comments. Often indicate a known-broken path the author meant to fix.

Why it matters: Each marker is an unfinished thought. Production code shouldn't ship with debt that's documented but not tracked.

How AI causes it: AI mirrors the style of the codebase, so existing TODOs propagate into new code.

Fix approach: Convert each into a ticket. Delete the comment when the ticket lands. Use a pre-commit hook to block new TODOs without an issue link.

1 matching finding on this repo

low Old/deprecated-named symbol `addLegacy` in docs/site/docusaurus.config.js:155

View all legacy markers findings →

Commented-out code 4 findings

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

4 matching findings on this repo

info Commented-code block (6 lines) in docs/site/src/shared/js/utils.js:111
info Commented-code block (6 lines) in docs/site/src/shared/components/ImportContent…
info Commented-code block (7 lines) in docs/site/src/shared/plugins/inject-code/step…
info Commented-code block (10 lines) in docs/site/src/scripts/transform-walrus-memor…

View all commented-out code findings →

Config drift 5 findings

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

5 matching findings on this repo

medium Dockerfile runs as root: docker/walrus-antithesis/build-test-config-image/Docke…
critical Possible secret in crates/walrus-sui/src/client/rpc_config.rs crates/walrus-sui/src/client/rpc_config.rs:312
low Very large file: crates/walrus-service/src/node/config.rs (3404 lines)
low Very large file: crates/walrus-service/src/node/storage/database_config.rs (135…
low Old/deprecated-named symbol `addLegacy` in docs/site/docusaurus.config.js:155

View all config drift findings →

For AI agents: Voting guide (TP/FP) MCP manifest Stdio wrapper SARIF Integrate Findings queue Vote TP/FP on findings to calibrate the engine.

For AI agents + API integrations

Email me when this repo regresses

Free. We re-scan periodically; new criticals → your inbox. No signup required for the scan itself.

API access

This page is publicly accessible at: https://repobility.com/scan/ff188cb4-168c-4344-8a06-1c572ad3f0f5/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ff188cb4-168c-4344-8a06-1c572ad3f0f5/

Important — please don't re-submit the same URL repeatedly. The submission endpoint is idempotent: re-submitting the same git URL returns this same scan_token, not a new one. To re-scan this repo, sign up free and use the dashboard.