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

RoyRizkallah/IOT

https://github.com/RoyRizkallah/IOT · scanned 2026-06-15 23:56 UTC (2 months, 3 weeks ago)

32 raw signals (0 security + 32 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
73.0
/100
Security checks
73
0 findings
System graph
73
100.0% cov · 30 findings
Critical
10
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 10 High 0 Medium 6 Low 12 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 30 Crowd 0 Layer: Software 1 Hardware 3 Frontend 1 Security 11 Cicd 1 Quality 10 Api 3

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

#1
Possible secret in pi_setup.py
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 pi_setup.py:9; move to env var / secrets manager.
pi_setup.py:9
#2
Possible secret in check_logs.py
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 check_logs.py:5; move to env var / secrets manager.
check_logs.py:5
#3
Possible secret in check_pi.py
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 check_pi.py:5; move to env var / secrets manager.
check_pi.py:5
#4
Possible secret in start_pi.py
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 start_pi.py:5; move to env var / secrets manager.
start_pi.py:5
#5
Possible secret in connect_wifi.py
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 connect_wifi.py:5; move to env var / secrets manager.
connect_wifi.py:5
#6
Possible secret in read_pi_files.py
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 read_pi_files.py:5; move to env var / secrets manager.
read_pi_files.py:5
#7
Possible secret in verify_pi.py
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 verify_pi.py:5; move to env var / secrets manager.
verify_pi.py:5
#8
Possible secret in fix_buzzer_pin.py
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 fix_buzzer_pin.py:5; move to env var / secrets manager.
fix_buzzer_pin.py:5
#9
Possible secret in patch_buzzer_control.py
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 patch_buzzer_control.py:19; move to env var / secrets manager.
patch_buzzer_control.py:19
#10
Possible secret in deploy_buzzer.py
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 deploy_buzzer.py:386; move to env var / secrets manager.
deploy_buzzer.py:386

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/f24591b6-9e71-4cce-8b33-7872d0fb4ede/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f24591b6-9e71-4cce-8b33-7872d0fb4ede/

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.