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.
Sign up free Scan another repo

syntax-tz/smart

https://github.com/syntax-tz/smart · scanned 2026-06-16 00:28 UTC (2 months, 2 weeks ago)

269 raw signals (0 security + 269 graph)

File as issue Image
UNIFIED Repobility · multi-layer engine · AI coders

Complete repo analysis

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

JSON
Combined
41.2
/100
Security checks
41
0 findings
System graph
41
100.0% cov · 262 findings
Critical
1
click to filter
Agents
10
0 votes
Crowd
0
reported
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 1 High 1 Medium 31 Low 20 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Security checks 0 System graph 262 Crowd 0 Layer: Frontend 54 Network 1 Hardware 4 Security 22 Cicd 2 Quality 167 Api 12
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 41.2/100 with 100.0% coverage. It contains 5940 nodes across 30 cross-layer flows, written primarily in mixed languages. Engine surfaced 269 findings — concentrated in quality (167), frontend (54), security (22). Risk profile is high: 1 critical, 1 high, 35 medium. Recommended next step: open the quality layer findings first — that's where the highest-impact wins live.

Showing 53 of 262 actionable findings. 269 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 Possible secret in .github/workflows/ci.yml
Detected pattern matching password_literal. Rotate the credential and move to a secret manager.
.github/workflows/ci.yml:152
high System graph security Secrets conf 1.00 Runtime dotenv file present in repo: web/.env.development
`web/.env.development` looks like a runtime dotenv file. No high-confidence secret value was matched, but runtime dotenv files often drift into live credentials. Move real values to a secret manager and keep only `.env.example` style templates in source control.
web/.env.development ConfigEnv fileRuntime env
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/features/marketing/components/marketing-layout.tsx:36
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph frontend Frontend quality conf 1.00 `dangerouslySetInnerHTML` used in a React component — web/src/shared/components/ui/chart.tsx:80
Open XSS surface unless the input is provably trusted. Replace with explicit JSX or sanitize via a vetted library. Why: OWASP basics. Already partially flagged by the security analyzer. Rule id: fq.dangerous-html
Fq dangerous html
medium System graph quality Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — docs/design/mwangazza-v1/design-canvas.jsx:136
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 Integrity conf 1.00 `fetch()` without try/.catch or AbortSignal — web/src/shared/lib/chunk-reload.ts:20
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/commands/handoff.md
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/commands/handoff.md 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. 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 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 hardware Security conf 1.00 Dockerfile runs as root: backend/Dockerfile
No non-root USER set. Containers running as root expand the blast radius of any vulnerability inside the image.
Container
medium System graph cicd CI/CD security conf 1.00 5 occurrences GitHub Action is tag-pinned rather than SHA-pinned
pnpm/action-setup@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
3 files, 5 locations
.github/workflows/ci.yml:29, 49 (2 hits)
.github/workflows/codeql.yml:42, 49 (2 hits)
.github/workflows/mobile-ci.yml:32
CI/CD securitySupply chainGithub actions
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in docs/design/mwangazza-v1/product/Timetable/Timetable Planner.html:813
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
docs/design/mwangazza-v1/product/Timetable/Timetable Planner.html:813 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/features/marketing/components/marketing-layout.tsx:36
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/features/marketing/components/marketing-layout.tsx:36 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'dangerous_innerhtml' in web/src/shared/components/ui/chart.tsx:80
Found a known-risky pattern (dangerous_innerhtml). Review and replace if possible.
web/src/shared/components/ui/chart.tsx:80 Dangerous innerhtml
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mobile/pages/Nomi_v6.html:4742
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mobile/pages/Nomi_v6.html:4742 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mobile/pages/SMART Mobile Design System v7.html:1643
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mobile/pages/SMART Mobile Design System v7.html:1643 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/assets/craft.js:27
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/assets/craft.js:27 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/assets/ecosystem.js:14
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/assets/ecosystem.js:14 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/assets/wordmark.js:107
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/assets/wordmark.js:107 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/Mwangazza - Design System.html:14441
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/Mwangazza - Design System.html:14441 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/Mwangazza - Logo Family Sheet.html:213
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/Mwangazza - Logo Family Sheet.html:213 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/Mwangazza - ZZ Icon & Favicon.html:374
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/Mwangazza - ZZ Icon & Favicon.html:374 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/attendance.html:903
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/attendance.html:903 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/cal-v3.js:649
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/cal-v3.js:649 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/comms.html:882
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/comms.html:882 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/finance.html:754
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/finance.html:754 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/home.html:816
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/home.html:816 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/marks.html:500
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/marks.html:500 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/Timetable/Timetable Planner.html:935
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/Timetable/Timetable Planner.html:935 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/mwangazza-v1/product/Timetable/tt-setup.html:1062
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/mwangazza-v1/product/Timetable/tt-setup.html:1062 Direct innerhtml assignment
medium System graph security security conf 1.00 Insecure pattern 'direct_innerhtml_assignment' in docs/design/web/SMART-Web-Design-System-v2.html:14419
Found a known-risky pattern (direct_innerhtml_assignment). Review and replace if possible.
docs/design/web/SMART-Web-Design-System-v2.html:14419 Direct innerhtml assignment
medium System graph quality Placeholder conf 1.00 Placeholder or mock-heavy implementation detected
Found 232 placeholder/mock markers across 108 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 network Security conf 1.00 Privileged port 30 in use
Port 30 is privileged (<1024). Make sure the service runs with the right caps or front it with a non-privileged port via a load balancer.
.github/workflows/codeql.yml Ports
low System graph frontend Frontend quality conf 1.00 "active" state uses light bg in a dark theme — web/src/features/calendar/components/canon.tsx:137
A ternary like `active ? 'bg-white' : '...'` (or bg-gray-100/200) on a dark theme produces jarring white pills. Use a dark-emphasized active state instead — border + ring or slightly brighter dark bg. Example: `active ? 'bg-gray-800 border-gray-500 ring-1 ring-blue-500/30' : '…'`. Why: P-E in CHEC…
Fq active light bg
low System graph hardware Coverage conf 1.00 Containers defined but no K8s/orchestration manifest found
Repo has Dockerfiles/compose but no Kubernetes/Nomad manifests. If the target deployment is K8s, the manifests may live in a separate ops repo.
Deployment
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/aspnet:10.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:17 containersPinned dependencies
low System graph hardware Supply chain conf 1.00 Docker base image is tag-pinned but not digest-pinned: mcr.microsoft.com/dotnet/sdk:10.0
Container tags can be retagged upstream. Pin production base images to a reviewed digest (`image@sha256:...`) when reproducibility and supply-chain integrity matter.
backend/Dockerfile:1 containersPinned dependencies
low System graph cicd CI/CD security conf 1.00 4 occurrences GitHub Action is tag-pinned rather than SHA-pinned
actions/setup-node@v6 can move without a code change in this repo. Pin third-party actions to a reviewed 40-character commit SHA.
2 files, 4 locations
.github/workflows/ci.yml:35, 55, 104 (3 hits)
.github/workflows/codeql.yml:39
CI/CD securitySupply chainGithub actions
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 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
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/forgot-password
`web/src/features/auth/api/mutations.ts` declares `POST /auth/forgot-password` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/logout
`web/src/features/auth/api/mutations.ts` declares `POST /auth/logout` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /auth/resend-invitation
`web/src/features/auth/api/mutations.ts` declares `POST /auth/resend-invitation` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /contact
`web/src/features/marketing/lib/contact-api.ts` declares `POST /contact` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /finance/invoices/generate
`web/src/features/finance/hooks/mutations.ts` declares `POST /finance/invoices/generate` 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 co…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /school/onboarding/complete
`web/src/features/onboarding/hooks/mutations.ts` declares `POST /school/onboarding/complete` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /school/onboarding/dismiss
`web/src/features/onboarding/hooks/mutations.ts` declares `POST /school/onboarding/dismiss` 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…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /school/onboarding/position
`web/src/features/onboarding/hooks/mutations.ts` declares `POST /school/onboarding/position` 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 wh…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: POST /school/onboarding/resume
`web/src/features/onboarding/hooks/mutations.ts` declares `POST /school/onboarding/resume` 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 …
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /schedule/settings
`web/src/features/schedule/hooks/mutations.ts` declares `PUT /schedule/settings` 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 i…
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /school/details
`web/src/features/settings/hooks/mutations.ts` declares `PUT /school/details` 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.
Unused endpoint
low System graph api Wiring conf 1.00 Unused endpoint: PUT /school/settings
`web/src/features/settings/hooks/mutations.ts` declares `PUT /school/settings` 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.
Unused endpoint
low System graph quality Complexity conf 1.00 Very large file: docs/design/mwangazza-v1/design-canvas.jsx (974 lines)
Files with >800 lines often hide complexity hotspots and discourage tests.
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/f5bbda4f-3133-4dd4-b7dc-c848259c7011/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/f5bbda4f-3133-4dd4-b7dc-c848259c7011/

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.