sayedmuntasir0027-glitch/Linear-Search-with-c

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.55s · analysis 0.04s · GitHub preflight 557ms

sayedmuntasir0027-glitch/Linear-Search-with-c

https://github.com/sayedmuntasir0027-glitch/Linear-Search-with-c.git · scanned 2026-05-26 14:56 UTC (1 week, 2 days ago) · 10 languages

10 findings (2 legacy + 8 scanner) Scanner says 85 (lower by 17)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 2 days ago · v2 · 6 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`	40.0	0.15	6.00
`practices_score`	70.0	0.15	10.50
`code_quality`	80.0	0.10	8.00
Overall		1.00	68.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

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

Showing 4 of 6 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 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.

coverageauth

medium 9-layer cicd coverage conf 1.00 No CI/CD pipelines detected

No GitHub Actions, GitLab CI, or CircleCI configs found. Without CI you can't gate deploys on tests/lints.

coverage

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/817a449e-d4b2-4214-af93-3e7aafde3bc6/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/817a449e-d4b2-4214-af93-3e7aafde3bc6/

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.