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.

ahmedhmmad/tawexam

https://github.com/ahmedhmmad/tawexam · scanned 2026-06-17 01:29 UTC (1 month, 2 weeks ago)

13 raw signals (0 security + 13 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 2 weeks ago · v2 · last Δ -6.6 (diff) · 10 actionable findings from 1 signal source. 3 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 10 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

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

Showing 10 of 10 actionable findings. 13 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 security conf 1.00 Insecure pattern 'private_key_in_repo' in backend/jest.setup.cjs:7

Found a known-risky pattern (private_key_in_repo). Review and replace if possible.

backend/jest.setup.cjs:7 Private key in repo

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in .env.example

Detected pattern matching private_key. Rotate the credential and move to a secret manager.

lines 7, 9

.env.example:7, 9 (2 hits)

critical System graph security Secrets conf 1.00 2 occurrences Possible secret in backend/jest.setup.cjs

Detected pattern matching private_key. Rotate the credential and move to a secret manager.

lines 7, 9

backend/jest.setup.cjs:7, 9 (2 hits)

medium System graph hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

medium System graph hardware Security conf 1.00 Dockerfile runs as root: nginx/Dockerfile

No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.

Container

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 Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: nginx:alpine

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

nginx/Dockerfile:1 containersPinned dependencies

low System graph hardware Supply chain conf 1.00 2 occurrences Docker base image is tag-pinned but not digest-pinned: node:20-alpine

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

lines 1, 16

backend/Dockerfile:1, 16 (2 hits)

containersPinned dependencies

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

12 tests / 81 src (ratio 0.15).

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

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/2aacdba0-2c7a-4a17-9711-87b7b1dd610e/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/2aacdba0-2c7a-4a17-9711-87b7b1dd610e/

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.