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
Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.
Scan summary Repository scanned at 73.0/100 with 100.0% coverage. It contains 469 nodes across 5 cross-layer flows, written primarily in mixed languages. Engine surfaced 32 findings — concentrated in quality (12), security (11), hardware (3). Risk profile is high: 10 critical, 0 high, 6 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 28 of 30 actionable findings. 32 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 Possible secret in check_logs.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
check_logs.py:5
critical System graph security Secrets conf 1.00 Possible secret in check_pi.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
check_pi.py:5
critical System graph security Secrets conf 1.00 Possible secret in connect_wifi.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
connect_wifi.py:5
critical System graph security Secrets conf 1.00 Possible secret in deploy_buzzer.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
deploy_buzzer.py:386
critical System graph security Secrets conf 1.00 Possible secret in fix_buzzer_pin.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
fix_buzzer_pin.py:5
critical System graph security Secrets conf 1.00 Possible secret in patch_buzzer_control.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
patch_buzzer_control.py:19
critical System graph security Secrets conf 1.00 Possible secret in pi_setup.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
pi_setup.py:9
critical System graph security Secrets conf 1.00 Possible secret in read_pi_files.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
read_pi_files.py:5
critical System graph security Secrets conf 1.00 Possible secret in start_pi.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
start_pi.py:5
critical System graph security Secrets conf 1.00 Possible secret in verify_pi.py
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
verify_pi.py:5
medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data
A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.
Mock dataCritical flowGenerated repo pattern
medium System graph hardware Security conf 1.00 Dockerfile runs as root: sentry_agent/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — test_buzzer_gpio.py:7
`subprocess.run(...)` here lacks both a `timeout=` arg and an enclosing try/except. This is exactly the class of bug that took down our git-clone earlier (HTTP/2 stream cancel surfaced as a fatal). Add a `timeout=` and wrap in try/except, or use a wrapper that retries.
runtime safetyRobustness
medium System graph security Coverage conf 1.00 No auth library detected
The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.
auth
medium System graph cicd CI/CD security conf 1.00 No CI/CD pipelines detected
No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.
CI/CD securityCoverage
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 17 placeholder/mock markers across 8 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.
Mock dataIncompleteGenerated repo pattern
low System graph quality Production readiness conf 1.00 Composite production-readiness gap
Multiple low-cost hardening controls are missing together: license, ci. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.
Repo hardeningGenerated repo pattern
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph quality Debug conf 1.00 Debug logging residue appears in source files
Found 99 console/debugger/print-style debug statements in non-test source. This is a common fast-generation residue before production cleanup.
CleanupRepo hardeningGenerated repo pattern
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: python:3.12-slim
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
sentry_agent/Dockerfile:9 containersPinned dependencies
low System graph quality Integrity conf 1.00 3 occurrences Near-duplicate function bodies in 2 places
Functions with the same first-5-line body hash: sentry_agent/sentry/__main__.py:serve, sentry_agent/sentry/__main__.py:mock This is *the* AI-coder failure mode (4× more duplication in vibe-coded repos — see https://jw.hn/ai-code-hygiene). Consolidate or document why they're separate.
3 occurrences
repo-level (3 hits)
duplicatesduplication
low System graph quality License conf 1.00 No license file detected
No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.
Repo hardeningGenerated repo pattern
low System graph quality Integrity conf 1.00 Old/deprecated-named symbol `model_copy` in sentry_agent/tests/test_storage.py:132
Names with suffixes like `_old`, `_v1`, `_deprecated` usually indicate replaced-but-not-removed code (typical AI-coder leftover). Confirm and delete, or rename if it's the active version.
old markerDead code
low System graph software Dead code conf 1.00 Possibly dead Python function: register
No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.
sentry_agent/sentry/mqtt/bus.py:77
low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence
The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.
Git historyGenerated repo pattern
low System graph api Wiring conf 1.00 Unused endpoint: GET /
`sentry_agent/sentry/camera/relay.py` declares `GET /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /snapshot.jpg
`sentry_agent/sentry/camera/relay.py` declares `GET /snapshot.jpg` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: GET /stream.mjpeg
`sentry_agent/sentry/camera/relay.py` declares `GET /stream.mjpeg` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.
Unused endpoint
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.