Full-codebase-audit 2026-05-30 outputs: - Audit report: 09 - Audits/Full Codebase Audit - 2026-05-30.md - 81 issue files ISSUE-055..135 (decisions + 1 skipped no-brainer). - Scanner docs from scratch (was zero): architecture, data model, API ref, payment flow, operations runbook + repo README. - Doc-sync updates across API reference, data models, flows, design system. - Secret Rotation Runbook (08 - Operations) for the exposed credentials. - Reusable workflow guide (07 - Development) + .claude/workflows/full-codebase-audit.js. Issues remain status:open intentionally — the code fixes are uncommitted-then-committed working-tree changes per repo and aren't "resolved" until merged/deployed. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
issue, title, severity, domain, labels, status, created, source
| issue | title | severity | domain | labels | status | created | source | ||
|---|---|---|---|---|---|---|---|---|---|
| 134 | Frontend: Sentry source-map upload configured but no auth token injected | low | Observability |
|
open | 2026-05-30 | Full Codebase Audit 2026-05-30 |
Frontend: Sentry source-map upload configured but no auth token injected
Severity: low Domain: Observability Labels: frontend, configuration
Description
frontend/next.config.ts:83 uses withSentryConfig with source-map upload enabled, but SENTRY_AUTH_TOKEN, SENTRY_ORG, and SENTRY_PROJECT are not injected in CI. Source maps are not actually uploaded, making stack traces in Sentry unreadable.
Options
- Inject
SENTRY_AUTH_TOKEN/ORG/PROJECTvia CI so maps actually upload. - Disable
withSentryConfigupload to save build time if Sentry is unused. - Keep config but document that uploads are intentionally off.
Recommendation
Decide whether Sentry is in use: if yes, inject the secrets in CI; if no, disable the upload plugin.
Affected Files
frontend/next.config.ts:83frontend/.woodpecker/production.yml— CI secrets
References
- Full Codebase Audit 2026-05-30 — DEC-79