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.

yannabadie/YGN-SAGE

https://github.com/yannabadie/YGN-SAGE · scanned 2026-06-16 01:05 UTC (2 months, 1 week ago)

343 raw signals (0 security + 343 graph)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 1 week ago · v1 · 295 actionable findings from 1 signal source. 48 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Possible secret in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:7; move to env var / secrets manager.
docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:7
#2
Possible secret in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:7; move to env var / secrets manager.
docs/benchmarks/2026-04-29-cycle7-evidence-bcb-N50-official-grade.json:7
#3
Possible secret in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:23; move to env var / secrets manager.
docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:23
#4
Possible secret in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:23; move to env var / secrets manager.
docs/benchmarks/2026-04-29-path-e-step3-bcb-official-grade.json:23
#5
Insecure pattern 'private_key_in_repo' in sage-python/src/sage/security/redaction.py:19
GapSeverity.CRITICAL Layer.SECURITY score 0.550
Why: critical severity · OWASP-class risk
sage-python/src/sage/security/redaction.py:19
#6
Insecure pattern 'tls_verify_false' in CLAUDE.md:10
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
CLAUDE.md:10
#7
Insecure pattern 'tls_verify_false' in scripts/exocortex_ingest.py:50
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
scripts/exocortex_ingest.py:50
#8
Insecure pattern 'exec_used' in sage-core/src/verification/smt.rs:1150
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
sage-core/src/verification/smt.rs:1150
#9
Insecure pattern 'eval_used' in sage-core/src/sandbox/validator.rs:242
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
sage-core/src/sandbox/validator.rs:242
#10
Insecure pattern 'exec_used' in sage-core/src/sandbox/validator.rs:235
GapSeverity.HIGH Layer.SECURITY score 0.413
Why: high severity · OWASP-class risk
sage-core/src/sandbox/validator.rs:235

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/2dfff0fd-3692-40a2-ae24-673ff6cd81b7/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2dfff0fd-3692-40a2-ae24-673ff6cd81b7/

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.