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.

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

Scan timing: clone 2.61s · analysis 20.51s · 6.8 MB · GitHub API rate-limit (preflight)

mastomii/nexss

https://github.com/mastomii/nexss · scanned 2026-06-17 03:51 UTC (1 month, 1 week ago) · 10 languages

143 raw signals (109 security + 34 graph) 0th percentile · Typescript · small (2-20K LoC) System graph score 74 (lower by 35)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 1 month, 1 week ago · v1 · 118 actionable findings from 2 signal sources. 25 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

88.9% cov · 32 findings

Score breakdown â 2026-05-18-v5

Component	Sub-score	Weight	Contribution
`structure_score`	100.0	0.15	15.00
`security_score`	0.8	0.25	0.20
`testing_score`	0.0	0.20	0.00
`documentation_score`	63.1	0.15	9.46
`practices_score`	52.0	0.15	7.80
`code_quality`	66.3	0.10	6.62
Overall		1.00	39.1

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 2 High 43 Medium 34 Low 23 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 86 System graph 32 Crowd 0 Layer: Quality 31 Security 21 Software 50 Cicd 5 Api 1 Frontend 9 Hardware 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.

Config drift 1 finding

What it is: Settings duplicated across env files, Docker compose, K8s, and code defaults, all with slightly different values.

Why it matters: Production behaviour depends on whichever copy your loader reads first. Subtle bugs in staging that don't reproduce in dev.

How AI causes it: AI writes new config from memory rather than reading the existing source.

Fix approach: Pick one source of truth (env vars + a settings module). Have every other place import from there. Lint for duplicates in CI.

1 matching finding on this repo

medium No CI/CD configuration found

View all config drift 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/7f330887-921c-4316-9fdc-23c4726f09d4/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/7f330887-921c-4316-9fdc-23c4726f09d4/

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.