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
128 of your 248 findings came from Repobility's proprietary detections. ✓ Repobility tags below mark them.
Upstream (GitHub) caused delay on this scan — not Repobility.
  • GitHub API rate-limited (HTTP 403) — preflight skipped, fell back to direct git clone.
  • Clone from GitHub took 45.94s for a 118.8 MB repo slow.
  • Repobility's analysis ran in 15.57s after the clone landed.

immich-app/immich

https://github.com/immich-app/immich · scanned 2026-06-05 06:05 UTC (7 hours, 19 minutes ago) · 10 languages

962 findings (222 legacy + 740 scanner) 11/13 scanners ran Scanner says 51 (higher by 29)

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

Complete repo analysis

Last scanned 7 hours, 19 minutes ago · v2 · 592 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
Combined
65.3
/100
Repobility
80
222 legacy
9-layer
51
100.0% cov · 370 gaps
Critical
98
click to filter
Agents
6
0 votes
Crowd
0
reported
Score breakdown â 2026-05-18-v5
Component Sub-score Weight Contribution
structure_score 60.0 0.15 9.00
security_score 100.0 0.25 25.00
testing_score 68.0 0.20 13.60
documentation_score 76.0 0.15 11.40
practices_score 91.0 0.15 13.65
code_quality 70.0 0.10 7.00
Overall 1.00 79.7
security_score may be inflated — optional security scanners were skipped on this fast scan
Severity distribution — click a segment to filter
Active filters: excluding tests × Reset all
Severity: Critical 98 High 131 Medium 53 Low 219 9-Layer: Software Security Quality Integrity Frontend Hardware Data Network Cicd Source: Legacy 222 9-layer 370 Crowd 0 Layer: Quality 213 Security 92 Cicd 36 Software 88 Frontend 94 Network 8 Hardware 8 Api 53

Top 10 actions, ranked by impact × ease. Severity drives impact; tag-based fix-clarity drives ease.

#1
Possible secret in packages/sdk/src/fetch-client.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in packages/sdk/src/fetch-client.ts:7061; move to env var / secrets manager.
packages/sdk/src/fetch-client.ts:7061
#2
Possible secret in web/src/lib/constants.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in web/src/lib/constants.ts:257; move to env var / secrets manager.
web/src/lib/constants.ts:257
#3
Possible secret in server/src/enum.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/src/enum.ts:5; move to env var / secrets manager.
server/src/enum.ts:5
#4
Possible secret in server/src/enum.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/src/enum.ts:150; move to env var / secrets manager.
server/src/enum.ts:150
#5
Possible secret in server/src/emails/welcome.email.tsx
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/src/emails/welcome.email.tsx:67; move to env var / secrets manager.
server/src/emails/welcome.email.tsx:67
#6
Possible secret in server/src/services/notification-admin.service.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/src/services/notification-admin.service.ts:72; move to env var / secrets manager.
server/src/services/notification-admin.service.ts:72
#7
Possible secret in server/src/repositories/email.repository.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in server/src/repositories/email.repository.ts:37; move to env var / secrets manager.
server/src/repositories/email.repository.ts:37
#8
Possible secret in e2e/src/fixtures.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in e2e/src/fixtures.ts:11; move to env var / secrets manager.
e2e/src/fixtures.ts:11
#9
Possible secret in e2e/src/fixtures.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in e2e/src/fixtures.ts:34; move to env var / secrets manager.
e2e/src/fixtures.ts:34
#10
Possible secret in e2e/src/fixtures.ts
GapSeverity.CRITICAL Layer.SECURITY score 1.000
Why: critical severity · a leaked credential is a worst-case bug · fix is short / mechanical
Fix: Rotate the credential and remove it from in e2e/src/fixtures.ts:39; move to env var / secrets manager.
e2e/src/fixtures.ts:39

Click "Find this gap" on any action above to jump to it on the Findings tab. Adjust the chip bar to filter by impact (severity), layer, or source.

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/8bf65db7-e63f-4bf5-80e5-17232878700e/

To check status programmatically (no auth required): 

curl -s https://repobility.com/api/v1/public/scan/8bf65db7-e63f-4bf5-80e5-17232878700e/

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.