dceaf82934
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.3 KiB
1.3 KiB
issue, title, severity, domain, labels, status, created, source
| issue | title | severity | domain | labels | status | created | source | |||
|---|---|---|---|---|---|---|---|---|---|---|
| 106 | Backend: dual lockfiles (yarn.lock + package-lock.json) diverge | medium | Dependencies |
|
open | 2026-05-30 | Full Codebase Audit 2026-05-30 |
Backend: dual lockfiles (yarn.lock + package-lock.json) diverge
Severity: medium Domain: Dependencies Labels: backend, ci-cd, dependencies
Description
backend/package.json:117 has both yarn.lock and package-lock.json in the repo, and they are not kept in sync. CI and production use npm; the packageManager field references yarn. The two lockfiles represent different resolved dependency trees, so local yarn installs and CI npm installs can diverge.
Options
- Standardize on npm +
package-lock.json(matches CI/prod), deleteyarn.lock, fixDockerfile.dev. - Standardize on yarn (matches
packageManagerfield), make CI use yarn. - Keep both but regenerate and pin.
Recommendation
Pick one (npm matches prod/CI), delete the other lockfile, align Dockerfiles, and regenerate.
Affected Files
backend/package.jsonbackend/yarn.lockbackend/package-lock.jsonbackend/Dockerfile.dev
References
- Full Codebase Audit 2026-05-30 — DEC-55