← Back to scan
File as GitHub Issue repo: friday-platform/friday-studio

Push this scan report to friday-platform/friday-studio

Click the green button below to open GitHub’s new-issue form, pre-filled with the report title, summary table, top findings, and an embedded score-card image. No authentication needed — you review on GitHub before submitting. Repobility is credited as the scanner.

Embedded score card image

This image will render at the top of the issue body. Hosted on Repobility, refreshes automatically after re-scans.

Repobility score card

Issue title

Secret-like setting is echoed into a password input value

Curate findings to include

Pick exactly which findings appear in the issue body. By default the top 5 are included. Uncheck noise, check what matters.

Top 5 (default)
Severity Rule Title File:line
CRIT SEC022 [SEC022] Database URL With Embedded Credential: A database connection URL contains an emb… apps/link/scripts/test-e2e.ts:15
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… apps/atlasd/routes/signals/platform.ts:216
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… apps/link/src/routes/oauth.ts:137
HIGH SEC020 [SEC020] Secret Printed to Logs: Debug or diagnostic code appears to print a credential-b… apps/link/scripts/test-e2e.ts:31
HIGH JRN009 Secret-like setting is echoed into a password input value apps/studio-installer/src/steps/ApiKeys…:137
HIGH AUC003 [AUC003] Object-level route lacks visible authorization: A route with an object id-like p… tools/webhook-tunnel/main.go:237
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. apps/atlasd/src/sweep-agent-browser-ses…:161
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. apps/atlasd/src/process-agent-executor.…:232
MED ERR002 [ERR002] Empty Catch Block: Empty catch blocks hide errors. scripts/build-studio.ts:522
MED DKR003 Compose service `platform` image uses the latest tag docker-compose.yml:1
MED AUC001 [AUC001] No Repobility access matrix policy found: The repository uses web/API frameworks… —
MED AIC003 Duplicated implementation block across source files apps/link/src/providers/notion.ts:28
MED AIC003 Duplicated implementation block across source files apps/link/src/providers/linear.ts:11
MED AIC003 Duplicated implementation block across source files apps/atlasd/src/signal-stream.ts:162
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/workspaces/mcp.ts:91
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/workspaces/mcp.ts:27
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/workspaces/integrati…:161
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/workspaces/chat.ts:85
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/chunked-upload.ts:137
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/agents/preflight.ts:86
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/agents/preflight.ts:83
MED AIC003 Duplicated implementation block across source files apps/atlasd/routes/agents/get.ts:34
MED AIC003 Duplicated implementation block across source files apps/atlas-cli/src/modules/sessions/ses…:23
MED DKR014 Dockerfile copies broad context with incomplete .dockerignore Dockerfile:41
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:1430
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:1429
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:1428
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:1426
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:694
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/src/atlas-daemon.ts:689
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/workspaces/config.ts:711
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/workspaces/cache-sal…:4
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/workspace-events.ts:88
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/workspace-events.ts:83
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/link.ts:45
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/instance-events.ts:48
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/instance-events.ts:6
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/elicitations/index.ts:14
MED JRN003 Frontend API reference is not matched by discovered backend routes apps/atlasd/routes/elicitations/index.ts:4
MED AUC002 [AUC002] Low visible authorization coverage in route inventory: Only 36.4% of discovered … —
MED AGT012 Agent control bridge may listen on a network interface without visible auth packages/bundled-agents/src/web/tools/f…:9
MED AGT013 Agent auto-approve or skip-permissions mode is easy to enable packages/config/src/permissions.ts:16
LOW DKR008 .dockerignore misses sensitive defaults .dockerignore
LOW DKC010 Compose service lacks no-new-privileges hardening docker-compose.yml:1
Reset to top 5 44 findings available (after auto-suppression of test files + won't-fix)

Issue body (markdown)

## Code-quality scan: `friday-platform/friday-studio`

**Score: 61/100 (B+)**  ·  50 findings  ·  scanned 2026-05-14 21:41 UTC  ·  367,575 LOC

| Severity | Count |
|---|---|
| CRITICAL | 1 |
| HIGH | 5 |
| MEDIUM | 36 |
| LOW | 2 |

📊 [Full filterable report](https://repobility.com/scan/a2ae3de0-60fb-4729-9276-34cc0cc14ef8/)  ·  ![scorecard](https://repobility.com/scan/a2ae3de0-60fb-4729-9276-34cc0cc14ef8/report.png?v=1778794885-s2)

### Top findings

1. **CRITICAL** `SEC022` — Database URL With Embedded Credential
   `apps/link/scripts/test-e2e.ts:15` · A07:2021 Identification & Authentication Failures
2. **HIGH** `SEC020` — Secret Printed to Logs
   `apps/atlasd/routes/signals/platform.ts:216` · A07:2021 Identification & Authentication Failures
3. **HIGH** `SEC020` — Secret Printed to Logs
   `apps/link/src/routes/oauth.ts:137` · A07:2021 Identification & Authentication Failures
4. **HIGH** `SEC020` — Secret Printed to Logs
   `apps/link/scripts/test-e2e.ts:31` · A07:2021 Identification & Authentication Failures
5. **HIGH** `JRN009` — Secret-like setting is echoed into a password input value
   `apps/studio-installer/src/steps/ApiKeys.svelte:137`

---

**Security note**: this issue is public. If any flagged finding is a real, exploitable vulnerability, please redirect to your `SECURITY.md` policy or open a [private security advisory](https://docs.github.com/en/code-security/security-advisories/guidance-on-reporting-and-writing-information-about-vulnerabilities/privately-reporting-a-security-vulnerability) instead. We're happy to close this and re-submit privately.

---

_Filed automatically. Close this issue if not useful — we won't refile. Full report: https://repobility.com/scan/a2ae3de0-60fb-4729-9276-34cc0cc14ef8/_
Already filed
This repo publishes a SECURITY.md policy and the scan contains 5 Critical/High security finding(s). Public issue filing would violate coordinated disclosure. Submit privately via the project's security reporting channel.
Megaproject â high spam risk
Could not determine 'friday-platform/friday-studio' star count (GitHub API rate-limited or unreachable). When in doubt about repo size, prefer opening a focused PR or a discussion rather than an issue.
I read the warnings â override Cancel

The button opens GitHubâs new-issue page in a new tab. You will see the title + body pre-filled â review, edit if you want, then click GitHubâs "Submit new issue" button. Repobility never posts anything on your behalf.

For real security findings on big repos: use the project's SECURITY.md or private advisory flow instead of a public issue.