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

samsmasm/samsmasm.github.io

https://github.com/samsmasm/samsmasm.github.io · scanned 2026-06-16 00:01 UTC (2 months, 3 weeks ago)

198 raw signals (0 security + 198 graph)

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

Complete repo analysis

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

JSON
Combined
52.2
/100
Security checks
52
0 findings
System graph
52
88.9% cov · 194 findings
Critical
21
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 21 High 0 Medium 149 Low 18 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 194 Crowd 0 Layer: Software 1 Api 1 Frontend 9 Security 154 Cicd 1 Quality 28

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

#1
Possible secret in tote/index.html
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 tote/index.html:354; move to env var / secrets manager.
tote/index.html:354
#2
Possible secret in ask-v1.0/script.js
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 ask-v1.0/script.js:3; move to env var / secrets manager.
ask-v1.0/script.js:3
#3
Possible secret in temp/index.html
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 temp/index.html:354; move to env var / secrets manager.
temp/index.html:354
#4
Possible secret in spectra/script.js
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 spectra/script.js:5; move to env var / secrets manager.
spectra/script.js:5
#5
Possible secret in scrim/script.js
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 scrim/script.js:5; move to env var / secrets manager.
scrim/script.js:5
#6
Possible secret in spin/index.html
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 spin/index.html:401; move to env var / secrets manager.
spin/index.html:401
#7
Possible secret in flare/script.js
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 flare/script.js:8; move to env var / secrets manager.
flare/script.js:8
#8
Possible secret in flippinghard/student.html
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 flippinghard/student.html:314; move to env var / secrets manager.
flippinghard/student.html:314
#9
Possible secret in flippinghard/teacher.html
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 flippinghard/teacher.html:422; move to env var / secrets manager.
flippinghard/teacher.html:422
#10
Possible secret in photos/index.html
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 photos/index.html:19; move to env var / secrets manager.
photos/index.html:19

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/5ee5afdf-eb6b-41d6-873a-91268d11cf91/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/5ee5afdf-eb6b-41d6-873a-91268d11cf91/

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.