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.

thoribanet-hassan/-salone_claude

https://github.com/thoribanet-hassan/-salone_claude · scanned 2026-06-16 00:35 UTC (2 months, 2 weeks ago)

31 raw signals (0 security + 31 graph)

File as issue Image

UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

Last scanned 2 months, 2 weeks ago · v1 · 20 actionable findings from 1 signal source. 11 repeated signals grouped for readability. Security checks, system graph analysis, and verified AI-agent feedback are merged into one review queue.

JSON

77.8% cov · 20 findings

Severity distribution — click a segment to filter

Active filters: excluding tests × Reset all

Severity: Critical 1 High 0 Medium 9 Low 5 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 20 Crowd 0 Layer: Api 1 Frontend 4 Security 2 Cicd 2 Quality 11

Exclude dismissed / FP Exclude test files

Corpus Intelligence Cross-corpus context (cohort percentile, top patterns, fix plan) is shown only on repositories you own. Sign up and connect your repo to view it.

Scan summary Repository scanned at 68.1/100 with 77.8% coverage. It contains 478 nodes across 14 cross-layer flows, written primarily in mixed languages. Engine surfaced 31 findings — concentrated in security (13), quality (11), frontend (4). Risk profile is high: 12 critical, 0 high, 9 medium. Recommended next step: open the security layer findings first — that's where the highest-impact wins live.

Showing 15 of 20 actionable findings. 31 raw detector signals were grouped into reader-sized issues. Click TP / FP to vote on a finding's accuracy — votes adjust the confidence weighting and improve detection across the platform.

critical System graph security Secrets conf 1.00 12 occurrences Possible secret in src/i18n/auth.ts

Detected pattern matching password_literal. Rotate the credential and move to a secret manager.

lines 53, 58, 64, 88, 93, 99, 123, 128, +4 more

src/i18n/auth.ts:53, 58, 64, 88, 93, 99, 123, 128, +4 more (12 hits)

medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — src/app/t/[token]/TicketView.tsx:141

Bare `fetch(...)` will throw an unhandled rejection on network failure. Wrap in try/catch, attach a `.catch(...)`, or pass an AbortSignal with a timeout.

runtime safetyRobustness

medium System graph quality Agent instructions conf 1.00 Agent authority lacks a verifier contract: .claude/launch.json

This agent instruction grants code or shell authority but does not state the verification gate that decides promotion. The recurring safe pattern is: LLM proposes; deterministic tests/build/security checks verify; only verified code promotes.

.claude/launch.json VerificationClaude instruction

medium System graph quality Agent instructions conf 1.00 Agent instructions exist but release-hardening basics are missing

AI-coder instruction files were found, but the repo is missing license, ci, tests. Treat this as a contract gap: the agent is guided, but the generated output is not yet guarded by the controls that make it repeatable.

Repo hardeningGenerated repo pattern

medium System graph quality Production readiness conf 1.00 Composite production-readiness gap

Multiple low-cost hardening controls are missing together: license, ci, tests. Opus verification showed these co-occurring gaps are a better readiness signal than reading each flag in isolation.

Repo hardeningGenerated repo pattern

medium System graph quality Placeholder conf 1.00 Critical user flow still appears backed by mock or placeholder data

A payment/auth/admin/order/billing-style flow contains mock, fake, TODO, dummy, or placeholder markers in runtime source. In the Fable corpus this is a high-leverage completeness smell: the app can look finished while the money, identity, or tenant flow is still scaffolded.

Mock dataCritical flowGenerated repo pattern

medium System graph security Coverage conf 1.00 No auth library detected

The scanner did not find any standard auth library (JWT, OAuth, NextAuth, Auth0, etc.). The repo has auth/admin/session surface indicators, so auth may live in custom code, in a separate service, or be missing.

auth

medium System graph cicd CI/CD security 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.

CI/CD securityCoverage

medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected

Found 28 placeholder/mock markers across 6 source files. This often means the repo looks complete while core flows still use generated scaffolding or fake data.

Mock dataIncompleteGenerated repo pattern

medium System graph quality Tests conf 1.00 Very low test-to-source ratio

0 test file(s) for 78 source file(s) (ratio 0.00). Consider adding integration or unit tests for critical paths.

Coverage

low System graph frontend Frontend quality conf 1.00 Icon-only button without accessible name — src/app/dashboard/page.tsx:540

A `<button>` whose only child is a single glyph or symbol needs `title=` or `aria-label=` so screen readers (and tooltips on hover) work. Why: P3 in CHECKLIST.md — icon-only buttons skipped a title. Rule id: fq.button.no-label

Fq button no label

low System graph quality Agent instructions conf 1.00 Multiple root agent instruction files without precedence

The repo has multiple top-level AI-coder instruction files. Without precedence rules, different agents may follow different policies.

Governance

low System graph quality License conf 1.00 No license file detected

No LICENSE/COPYING/NOTICE file was found. Generated repositories often omit licensing, which blocks reuse and automated intake.

Repo hardeningGenerated repo pattern

low System graph cicd CI/CD security conf 1.00 package.json defines install-time lifecycle scripts

preinstall/install/postinstall/prepare scripts execute during dependency installation. Review them carefully for network calls, obfuscation, shell execution, or credential access.

package.json CI/CD securitySupply chainNpm

low System graph quality Provenance conf 1.00 Shallow git history limits provenance confidence

The repository is a shallow clone. Origin/evolution analysis cannot distinguish fresh generation, imported legacy code, or long-lived human code with high confidence.

Git historyGenerated repo pattern

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/c19d70d8-746a-47ed-ad6d-ac6c9279e720/

To check status programmatically (no auth required):

curl -s https://repobility.com/api/v1/public/scan/c19d70d8-746a-47ed-ad6d-ac6c9279e720/

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.