[auth] BETTER_AUTH_TRUSTED_ORIGINS replaces the configured browser origins
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- authentication, security
Research direction
Read apps/nanocore/src/auth/better-auth.ts at the referenced line and the configuration contract in docs/specs/20260628-nanocore_config_identity_contract.md. Check how validated server.cors.origins reaches authentication and inspect the relevant tests. Done when the environment value cannot change authentication admission and configured origins still work.
Written by the indexing model from the issue text.
Description
Audit question Q-53 (consensus answer in docs/audits/20261030-independent_doc_audit_answers_p2b.md).
- Contract:
docs/specs/20260628-nanocore_config_identity_contract.mdrequires authentication and browser CORS to shareserver.cors.origins. - Defect:
apps/nanocore/src/auth/better-auth.ts:163lets the undeclaredBETTER_AUTH_TRUSTED_ORIGINSenvironment value replace the authentication origin list. - Fix: remove the override and use the validated configuration list. Add no replacement key.
- Tests: the environment value cannot change auth admission; configured origins still work.
Found by the independent documentation audit; answered by coordinator and consultant consensus under the engineer's delegation of 2026-10-30. v0.1.0.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 3h 54m
- Merged PRs (30d)
- 5
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lingkaix/openkit
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
bug doc-audit
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
All issues in lingkaix/openkit
Similar issues
-
area: triage theme: undefined
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
jhipster/generator-jhipster#35895 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
paperclipai/paperclip#18396 ·
Maintainers usually reply within 1 day
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#33380 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
chore other
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
alastair-smith/card-games#342 ·
Maintainers usually reply within 1 day