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.

silicondoritos/jetson-rt-stack

https://github.com/silicondoritos/jetson-rt-stack · scanned 2026-06-16 00:12 UTC (2 months, 2 weeks ago)

16 raw signals (0 security + 16 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON

77.8% cov · 16 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 0 High 0 Medium 5 Low 7 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 16 Crowd 0 Layer: Software 3 Network 1 Hardware 2 Frontend 1 Security 1 Quality 8

Exclude dismissed / FP Exclude test files

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 91.2/100 with 77.8% coverage. It contains 174 nodes across 0 cross-layer flows, written primarily in mixed languages. Engine surfaced 16 findings — concentrated in quality (8), software (3), hardware (2). Risk profile is low: 0 critical, 0 high, 5 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 12 of 16 actionable findings. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

medium System graph quality Tests conf 1.00 CI is configured but no tests are detected

A CI pipeline exists, but the scan found no test files to gate. Opus labeled this generated-code pattern as config theater: release machinery exists, but it has little behavioral signal.

CI/CDConfig theaterRepo hardening

medium System graph quality Integrity conf 1.00 Network/subprocess call without timeout or try/except — scripts/check_dmabuf_invariants.py:38

`subprocess.check_output(...)` 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 network Security conf 1.00 Privileged port 955 in use

Port 955 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.

ignite_jetson_av.sh Ports

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 8 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

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 40 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: ubuntu:22.04

Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.

Dockerfile:1 containersPinned dependencies

low System graph software Dead code conf 1.00 Possibly dead Python function: g

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/plot_zedx_metis_bench.py:116

low System graph software Dead code conf 1.00 Possibly dead Python function: generate_launch_description

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/zedx_vslam.launch.py:23

low System graph software Dead code conf 1.00 Possibly dead Python function: run_inference

No callers detected by AST scan in this repo. Could be exported for external callers or a framework handler.

scripts/detect_metis.py:157

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

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/7a17933e-5471-4ef2-aa9c-acf5ee88bf14/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7a17933e-5471-4ef2-aa9c-acf5ee88bf14/

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.