pacheco973008-ops/portifolio1

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

https://github.com/pacheco973008-ops/portifolio1.git · scanned 2026-05-27 21:09 UTC (1 week, 1 day ago) · 10 languages

21 findings (7 legacy + 14 scanner) 16th percentile · Python · tiny (<2K LoC) Scanner says 66 (lower by 23)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 week, 1 day ago · v2 · 14 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`	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	43.5

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

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

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

high 9-layer security auth conf 1.00 Flask mutation route `process_form` without `@login_required` — main.py:15

Flask route declares POST/PUT/DELETE/PATCH methods without an auth decorator. Add `@login_required` (Flask-Login) or equivalent.

main.py:15 authowaspauth.flask.unauth_route

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 Legacy quality quality conf 1.00 [SEC123] Production stack trace / debug output exposed: Debug mode left on in production exposes stack traces, environment variables, framework internals — sometimes triggers RCE (Django debug page with arbitrary template eval).

Set DEBUG=False / APP_DEBUG=false in production. Provide a generic 500 handler that logs to backend but returns a sanitized page to clients.

main.py:22 qualitylegacy

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

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

low 9-layer security owasp conf 1.00 Insecure pattern 'debug_true' in main.py:22

Found a known-risky pattern (debug_true). Review and replace if possible.

main.py:22 owaspdebug_true

low 9-layer api wiring conf 1.00 Unused endpoint: ANY /

`main.py` declares `ANY /` but no frontend code we scanned calls it. This is fine if the endpoint serves external clients (mobile app, third-party, server-side webhooks). Otherwise it's dead code — consider removing or documenting who consumes it.

wiringunused-endpoint

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/6fce3fb3-58fe-48e9-b0d8-a4ae0270e88a/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/6fce3fb3-58fe-48e9-b0d8-a4ae0270e88a/

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.