saiprasadbanavathu-tech/task1

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.13s · analysis 0.06s · GitHub API rate-limit (preflight)

https://github.com/saiprasadbanavathu-tech/task1.git · scanned 2026-05-27 06:27 UTC (1 week, 2 days ago) · 10 languages

14 findings (2 legacy + 12 scanner) 51st percentile · Python · tiny (<2K LoC) Scanner says 79 (lower by 14)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 8 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`	30.0	0.15	4.50
`security_score`	100.0	0.25	25.00
`testing_score`	70.0	0.20	14.00
`documentation_score`	20.0	0.15	3.00
`practices_score`	70.0	0.15	10.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	65.0

Severity distribution — click a segment to filter

Active filters: layer: quality × excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

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

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

medium Legacy quality practices conf 1.00 [CFG006] Missing .gitignore: No .gitignore file. Risk of committing secrets and build artifacts.

Add a .gitignore appropriate for your language/framework.

practiceslegacy

medium 9-layer 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.

testscoverage

low Legacy quality documentation No LICENSE file

Add a LICENSE file to your repository. Use choosealicense.com to pick the right license (MIT for permissive, Apache 2.0 for patent protection, GPL for copyleft).

documentationlegacy

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/d6b39eda-ae57-4e9d-a43a-6d7113fe7339/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/d6b39eda-ae57-4e9d-a43a-6d7113fe7339/

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.