ruvnet/RuView — Repobility public scan

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.

Sign up free Scan another repo

ruvnet/RuView

https://github.com/ruvnet/RuView · scanned 2026-07-23 19:40 UTC (4 days, 21 hours ago) · 10 languages

594 raw signals (77 security + 517 graph) 26th percentile · Rust · large (100-500K LoC)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 4 days, 21 hours ago · v6 · last Δ +7.8 (diff) · 523 actionable findings from 2 signal sources. 61 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

Security checks

100.0% cov · 490 findings

click to filter

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 3 High 131 Medium 270 Low 115 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 33 System graph 490 Crowd 0 Layer: Quality 141 Security 250 Cicd 10 Software 19 Frontend 17 Network 4 Hardware 2 Dependencies 74 Api 6

Exclude dismissed / FP Exclude test files

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1

Agent instruction/config may expose a secret: .claude/commands/github/issue-tracker.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/github/issue-tracker.md:68; move to env var / secrets manager.

.claude/commands/github/issue-tracker.md:68

#2

Agent instruction/config may expose a secret: .claude/commands/github/sync-coordinator.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/github/sync-coordinator.md:78; move to env var / secrets manager.

.claude/commands/github/sync-coordinator.md:78

#3

Agent instruction/config may expose a secret: .claude/commands/github/release-manager.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/github/release-manager.md:227; move to env var / secrets manager.

.claude/commands/github/release-manager.md:227

#4

Agent instruction/config may expose a secret: .claude/commands/github/repo-architect.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/github/repo-architect.md:228; move to env var / secrets manager.

.claude/commands/github/repo-architect.md:228

#5

Agent instruction/config may expose a secret: .claude/commands/github/pr-manager.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/github/pr-manager.md:92; move to env var / secrets manager.

.claude/commands/github/pr-manager.md:92

#6

Agent instruction/config may expose a secret: .claude/commands/hooks/post-task.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/hooks/post-task.md:103; move to env var / secrets manager.

.claude/commands/hooks/post-task.md:103

#7

Agent instruction/config may expose a secret: .claude/commands/sparc/tutorial.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/sparc/tutorial.md:59; move to env var / secrets manager.

.claude/commands/sparc/tutorial.md:59

#8

Agent instruction/config may expose a secret: .claude/commands/sparc/code.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/sparc/code.md:69; move to env var / secrets manager.

.claude/commands/sparc/code.md:69

#9

Agent instruction/config may expose a secret: .claude/commands/sparc/sparc.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/sparc/sparc.md:91; move to env var / secrets manager.

.claude/commands/sparc/sparc.md:91

#10

Agent instruction/config may expose a secret: .claude/commands/sparc/post-deployment-monitoring-mode.md

GapSeverity.HIGH Layer.SECURITY score 0.750

Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical

Fix: Rotate the credential and remove it from in .claude/commands/sparc/post-deployment-monitoring-mode.md:63; move to env var / secrets manager.

.claude/commands/sparc/post-deployment-monitoring-mode.md:63

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/ad982fad-13fd-4eb8-940c-33c7ef4b6332/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/ad982fad-13fd-4eb8-940c-33c7ef4b6332/

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.