@kaavee315checks…codex/propose-fix-for-clanker-claim-vulnerability → master2 files · +143 −1review: @sohamganatrareview: @anshugarg15updated 1w agoUserRole.ADMIN into invite creation.getOrgAPIAuthContext() and forward it to generateInviteCodeAndSendEmail instead of using UserRole.ADMIN in apps/apollo/src/pages/api/v3.1/org/clanker/create_claim.ts.metadata.roleToAssign as UserRole.ADMIN so a successful, authorized CLANKER_CLAIM still grants the intended admin mapping on redeem.apps/apollo/src/pages/api/v3.1/org/clanker/create_claim.test.ts that mocks getOrgAPIAuthContext, DB_CLANKER_CLAIM and InviteCode.generateInviteCodeAndSendEmail to assert the route forwards the authenticated role into the invite creation call while preserving roleToAssign: UserRole.ADMIN.pnpm --dir packages/lib bundle which succeeded and produced ESM/CJS outputs.pnpm --dir apps/apollo lint --fix which completed successfully.SKIP_VALIDATION=true pnpm --dir apps/apollo with-env vitest run src/pages/api/v3.1/org/clanker/create_claim.test.ts but it could not complete in this environment due to missing generated Prisma client artifacts (.prisma/client/default) and Doppler secrets; the test harness run therefore failed to execute the suite end-to-end here.pnpm --dir apps/apollo check-types surfaced unrelated workspace-wide generated-type / Prisma client issues in this environment and did not complete (pre-existing failures not caused by these changes).Based on git blame analysis of 2 file(s):
| Contributor | Contribution | Files |
|---|---|---|
| Rahul Tarak | 100% | 1 |
Based on git history, Rahul Tarak would be good reviewer(s) for this PR.
🤖 Based on git blame with recency weighting (recent edits count more).