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.
98 of your 133 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 12.03s · analysis 2.4s · 41.9 MB · GitHub API rate-limit (preflight)

Zie619/n8n-workflows

https://github.com/Zie619/n8n-workflows · scanned 2026-06-05 10:29 UTC (5 days, 15 hours ago) · 10 languages

402 raw signals (132 security + 270 graph) 11/13 scanners ran 52nd percentile · Python · small (2-20K LoC) System graph score 59 (higher by 11)

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 5 days, 15 hours ago · v2 · 142 actionable findings from 2 signal sources. 125 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 65.0 0.15 9.75
security_score 100.0 0.25 25.00
testing_score 9.0 0.20 1.80
documentation_score 87.0 0.15 13.05
practices_score 91.0 0.15 13.65
code_quality 63.0 0.10 6.30
Overall 1.00 69.5
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all

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

#1
Possible secret in workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json
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 workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:740; move to env var / secrets manager.
workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:740
#2
Possible secret in workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json
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 workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:754; move to env var / secrets manager.
workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:754
#3
Possible secret in workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json
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 workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:793; move to env var / secrets manager.
workflows/Splitout/1283_Splitout_Webhook_Automation_Webhook.json:793
#4
Possible secret in workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json
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 workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:740; move to env var / secrets manager.
workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:740
#5
Possible secret in workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json
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 workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:754; move to env var / secrets manager.
workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:754
#6
Possible secret in workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json
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 workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:793; move to env var / secrets manager.
workflows/Splitout/0457_Splitout_Webhook_Create_Webhook.json:793
#7
.env file present in repo: ai-stack/.env
GapSeverity.HIGH Layer.SECURITY score 0.750
Why: high severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from the file; move to env var / secrets manager.
#8
Insecure pattern 'private_key_in_repo' in workflows/Code/0924_Code_Respondtowebhook_Process_Webhook.json:206
GapSeverity.CRITICAL Layer.SECURITY score 0.550
Why: critical severity · OWASP-class risk
workflows/Code/0924_Code_Respondtowebhook_Process_Webhook.json:206
#9
FastAPI POST `reindex_workflows` without auth dependency — api_server.py:573
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in api_server.py:573.
api_server.py:573
#10
FastAPI POST `rate_workflow` without auth dependency — src/community_features.py:443
GapSeverity.HIGH Layer.SECURITY score 0.537
Why: high severity · OWASP-class risk
Fix: Add `user = Depends(get_current_user)` to the function signature in src/community_features.py:443.
src/community_features.py:443

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/4a7efed7-46a7-4006-9909-6a976d6f9d00/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/4a7efed7-46a7-4006-9909-6a976d6f9d00/

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.