SecureBananaLabs/bug-bounty

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.

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

Scan timing: clone 1.48s · analysis 6.02s · 0.1 MB · GitHub preflight 427ms

https://github.com/SecureBananaLabs/bug-bounty · scanned 2026-06-05 19:36 UTC (4 days, 16 hours ago) · 10 languages

100 raw signals (10 security + 90 graph) 58th percentile · Javascript · tiny (<2K LoC) System graph score 79 (lower by 13)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

88.9% cov · 44 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	75.0	0.15	11.25
`security_score`	97.4	0.25	24.35
`testing_score`	20.0	0.20	4.00
`documentation_score`	55.0	0.15	8.25
`practices_score`	67.0	0.15	10.05
`code_quality`	80.0	0.10	8.00
Overall		1.00	65.9

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 2 Medium 7 Low 39 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 10 System graph 44 Crowd 0 Layer: Software 25 Quality 4 Cicd 2 Frontend 5 Api 18

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.

Config drift 3 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.

3 matching findings on this repo

low File has no detected symbols: apps/api/src/config/env.js
low File has no detected symbols: apps/web/next.config.js
info TODO/FIXME marker in shipping code — apps/api/src/config/db.js:2

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/f1d68f9b-9d99-4068-a91a-44a8e353f39c/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/f1d68f9b-9d99-4068-a91a-44a8e353f39c/

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.