avaandkevinwedding/avaandkevinwedding

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 19.11s · analysis 0.15s · 25.4 MB · GitHub API rate-limit (preflight)

https://github.com/avaandkevinwedding/avaandkevinwedding.git · scanned 2026-05-28 05:27 UTC (2 weeks, 2 days ago) · 10 languages

34 raw signals (14 security + 20 graph) 11/13 scanners ran 47th percentile · Javascript · tiny (<2K LoC) System graph score 86 (lower by 25)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 2 days ago · v2 · 15 actionable findings from 2 signal sources. 9 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 · 5 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	90.0	0.15	13.50
`security_score`	100.0	0.25	25.00
`testing_score`	0.0	0.20	0.00
`documentation_score`	40.0	0.15	6.00
`practices_score`	67.0	0.15	10.05
`code_quality`	70.0	0.10	7.00
Overall		1.00	61.5

security_score may be inflated — optional security scanners were skipped on this fast scan

Severity distribution — click a segment to filter

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

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

Exclude dismissed / FP Exclude test files

Scan summary Quality grade C+ (62/100). Dimensions: security 100, maintainability 90. 14 findings (5 security). 789 lines analyzed.

Showing 5 of 15 actionable findings. 24 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.

medium Security checks quality Quality conf 0.70 Public web app has no Content Security Policy

Add a Content-Security-Policy header through the web framework or hosting config. For static apps, add a CSP meta tag that restricts default-src, script-src, connect-src, img-src, and frame-ancestors.

index.html

medium Security checks quality Quality conf 0.78 Public web service has no security.txt

Add /.well-known/security.txt with Contact, Expires, Canonical, Preferred-Languages, and Policy fields. Keep the contact endpoint monitored.

.well-known/security.txt

medium System graph cicd CI/CD security conf 1.00 GitHub Actions workflow grants broad write permissions

CI tokens with write permissions increase blast radius when an action, dependency, or PR workflow is compromised. Prefer job-level least-privilege permissions.

.github/workflows/deploy.yml CI/CD securitySupply chainGithub actions

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.). Either auth lives in custom code, in a separate service, or is missing.

auth

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

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

Coverage

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/c79e3e6f-c25b-47db-ad0c-f1794f770bf0/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c79e3e6f-c25b-47db-ad0c-f1794f770bf0/

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.