kaskydstoyey0u/whatsapp-webhook

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.

Scan timing: clone 1.38s · analysis 0.09s · GitHub preflight 405ms

https://github.com/kaskydstoyey0u/whatsapp-webhook.git · scanned 2026-05-25 23:44 UTC (1 week, 3 days ago) · 10 languages

26 findings (12 legacy + 14 scanner) 14th percentile · Javascript · tiny (<2K LoC) Scanner says 76 (lower by 30)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 3 days ago · v2 · 19 findings from 2 sources. Findings combine the legacy security pipeline AND the multi-layer engine (atlas, wiring, flows, ranked) AND verified AI agent contributions.

JSON

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	50.0	0.15	7.50
`security_score`	95.5	0.25	23.88
`testing_score`	0.0	0.20	0.00
`documentation_score`	10.0	0.15	1.50
`practices_score`	30.0	0.15	4.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	45.4

Severity distribution — click a segment to filter

Active filters: severity: high × excluding tests × Reset all

Severity: Critical 0 High 3 Medium 6 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 12 9-layer 7 Crowd 0 Layer: Quality 9 Security 5 Frontend 2 Cicd 1 Api 2

Exclude dismissed / FP Exclude test files

Scan summary Repository scanned at 75.5/100 with 66.7% coverage. It contains 7 nodes across 2 cross-layer flows, written primarily in mixed languages. Engine surfaced 7 findings — concentrated in frontend (2), api (2), security (1). Risk profile is low: 0 critical, 0 high, 3 medium. Recommended next step: open the frontend layer findings first — that's where the highest-impact wins live.

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

high Legacy quality quality conf 0.80 ✓ Repobility Express POST /webhook has no auth

Express route POST /webhook declared without an auth middleware in its handler chain. Destructive methods (POST/PUT/DELETE/PATCH) on unauthenticated routes are OWASP A01:2021 broken access control.

index.js:22 qualitylegacy

high Legacy security auth conf 0.74 [AUC002] Low visible authorization coverage in route inventory: Only 0.0% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.

Only 0.0% of discovered routes show nearby authentication, authorization, middleware, or public-route evidence.

authlegacy

high Legacy security auth conf 0.68 [AUC009] Sensitive function route lacks elevated authorization evidence: A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /webhook.

A route appears to perform a sensitive function such as export, invite, role, token, billing, or destructive action without elevated policy evidence. Endpoint: GET /webhook.

index.js:9 authlegacy

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/c1edb560-fa9f-40a6-83db-b76ecc3ebb74/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c1edb560-fa9f-40a6-83db-b76ecc3ebb74/

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.