imakris/sintra

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.

64 of your 86 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.

Scan timing: clone 3.59s · analysis 1.64s · 2.9 MB · GitHub preflight 410ms

http://github.com/imakris/sintra.git · scanned 2026-05-19 21:45 UTC (2 weeks, 2 days ago) · 10 languages

104 findings (86 legacy + 18 scanner) Scanner says 100 (lower by 22)

File as issue Image v2 schema

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 weeks, 2 days ago · v2 · 95 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`	55.0	0.15	8.25
`security_score`	96.0	0.25	24.00
`testing_score`	85.0	0.20	17.00
`documentation_score`	90.0	0.15	13.50
`practices_score`	70.0	0.15	10.50
`code_quality`	37.4	0.10	3.74
Overall		1.00	77.0

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

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

Exclude dismissed / FP Exclude test files

Bug-class explainers. Each card groups findings of the same shape — these are the patterns most likely to ship to prod and reappear in future scans unless you systematically fix the cause, not just the instance.

Fragile runtime 78 findings

What it is: Code that runs but breaks under predictable input — division by zero, missing keys, unbounded loops, off-by-one slicing.

Why it matters: Reaches production undetected because happy-path tests pass. First user with a weird input crashes the request.

How AI causes it: AI loves writing the happy path; doesn't probe edge cases unless explicitly asked.

Fix approach: Add property-based tests. Wrap external inputs with explicit validators. Use the framework's typed deserializer (Pydantic, attrs).

12 matching findings on this repo

medium Bare except continues silently tests/runner/platform/windows.py:220
medium Bare except continues silently tests/runner/platform/windows.py:212
medium Bare except continues silently tests/runner/platform/windows.py:198
medium Bare except continues silently tests/runner/platform/windows.py:90
medium Bare except continues silently tests/runner/platform/windows.py:40
medium Bare except continues silently tests/runner/platform/posix.py:327
medium Bare except continues silently tests/runner/platform/posix.py:322
medium Bare except continues silently tests/runner/platform/posix.py:314
medium Bare except continues silently tests/runner/platform/posix.py:296
medium Bare except continues silently tests/runner/platform/posix.py:187
medium Bare except continues silently tests/runner/platform/posix.py:122
medium Bare except continues silently tests/runner/platform/posix.py:51

View all fragile runtime findings →

Commented-out code 1 finding

What it is: Lines of source that were intentionally disabled but never deleted.

Why it matters: Git already remembers history — commented code rots, becomes wrong, and adds noise to diffs.

How AI causes it: AI sometimes comments out broken code instead of fixing it. Reviewers approve out of inertia.

Fix approach: Delete. Trust `git log`. If you really need to remember, save it in a notes file under `docs/`.

1 matching finding on this repo

info Commented-code block (11 lines) in tests/run_tests.py:122

View all commented-out code findings →

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/3d8c0053-0017-479e-b4b2-c9cd42938fbb/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/3d8c0053-0017-479e-b4b2-c9cd42938fbb/

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.