Security review of web app sign-in, invites and account deletion (TypeScript/Node)

$250-750 USD

Posted 1 minute ago

•

Ends in 6 days

$250-750 USD

Paid on delivery

We need a security review of a TypeScript/React PWA with a Hono server and Postgres. Review Apple and Google OAuth and magic-link sign-in, trip invitations, and account deletion. After a mutual NDA, you will get read-only GitHub access at a named commit; cloning and running locally is OK. No production or live testing. Deliver written findings by Monday November 16, 2026: severity, file/line, what could go wrong, and a recommended fix. Out of scope: building features, changing production, publishing write-ups, or sharing code. Budget about $250 (fixed-price).

Project ID: 40806448

About the project

91 proposals

Open for bidding

Remote project

Active 4 secs ago

Place your bid

Bid amount Email address

Benefits of bidding on Freelancer

Set your budget and timeframe

It's free to sign up and bid on jobs

91 freelancers are bidding on average $390 USD for this job

User Avatar
Flag of UNITED STATES

Hi, I am Elias from the sunny state of Florida. Your project on reviewing the security of the sign-in, invites, and account deletion in your TypeScript/React PWA is vital. Strong security not only protects user data but also builds trust. The real challenge here is identifying vulnerabilities in authentication flows and permission management. A common issue is overlooking potential attack vectors, especially in OAuth implementations and account deletion logic. The tricky part is ensuring security measures do not compromise user experience. My approach would involve a thorough audit of your current setup, focusing on potential vulnerabilities and suggesting mitigations. I prioritize balancing security and usability while ensuring the system is scalable for future needs. I've conducted similar security reviews for applications using Node.js and PostgreSQL, providing valuable insights into common risks. A few questions to better understand the scope: Q1 – What user roles and permissions are currently defined in your application? Q2 – Are there specific security standards or compliance requirements you want to adhere to? Q3 – How do you currently handle user session management and token expiration? Happy to discuss the details and suggest the best technical approach. Looking forward to hearing from you.

User Avatar
Flag of SERBIA

Hi, The OAuth flows and magic-link tokens are where attackers most often find account takeover: missing state validation, tokens stored insecurely, redirect URIs not locked down, or magic links that don't expire or check the user's IP. I'd review the Apple and Google OAuth implementations for state parameter handling and redirect validation, check how magic-link tokens are generated, stored and verified in Postgres, then trace the invitation flow to see if a link to someone else's trip can be claimed by the wrong account. Account deletion needs to confirm it actually removes all user data, not just soft-deletes it. I'd clone at the named commit, run locally without touching production, and step through each flow in the browser dev tools and database queries. The findings document will list each issue with the file and line, the security risk in plain terms, and a concrete fix. Send the NDA and GitHub link once signed, and I'll start with the OAuth state handling. Denis

User Avatar
Flag of NIGERIA

Hi, I'm excited to offer you a comprehensive security review for your TypeScript/React PWA with a Hono server and Postgres. Here’s what I will deliver: - A detailed review of Apple and Google OAuth and magic-link sign-in processes. - Security assessment of trip invitations and account deletion functionalities. - Written findings by Monday, November 16, 2026, covering severity, specific file/line vulnerabilities, potential issues, and recommended fixes. This review will focus on identifying and mitigating potential security risks without any production or live testing. I have extensive experience in this field and will ensure a thorough analysis. Feel free to check out my portfolio at https://www.freelancer.com/u/reedsystems for more insights. Looking forward to working with you!

User Avatar
Flag of INDIA

Hello Sir, I can conduct a comprehensive security review of your TypeScript/React PWA, focusing on Apple and Google OAuth, magic-link sign-in, trip invitations, and account deletion. Using my expertise in Node.js, PostgreSQL, and penetration testing, I will analyze your codebase for vulnerabilities, document findings with severity ratings, and provide actionable fixes. I am ready to start right away. Could you clarify any specific areas of concern you would like me to prioritize? Thanks, Deepak

User Avatar
Flag of UNITED KINGDOM

Hey, sounds like you need a thorough security review of the auth flows and account deletion logic on that TypeScript and Hono stack before Monday. I can audit the OAuth callbacks, magic links, and invite tokens locally against the specific commit you share. I usually check how session tokens are dropped and whether invite tokens can be reused or brute-forced. Are the invite tokens hashed in Postgres, or stored as plain strings right now?

User Avatar
Flag of BANGLADESH

Invite flows and account deletion are where a sign-in review stops being about OAuth and starts being about authorization. A magic link that works once is fine. One that survives a re-invite, or an invite token that grants access to someone else's trip, is a different bug class entirely. Deletion has the same shape. Removing the user row while trips, memberships, or PII stay in Postgres and backups is a compliance problem dressed up as a feature. I've done this kind of review on a crypto/fintech platform running 20+ microservices, where OAuth, session handling, and multi-tenant access control all had to hold up under real traffic. I read auth code the way an attacker would: token lifecycle, session fixation, object-level checks, race conditions on invite acceptance. I'd focus on Apple and Google token verification, magic-link expiry and reuse, and the deletion path end to end, then hand you a written report with severity and reproduction steps for each finding. Is account deletion already touching trips and memberships, or is that still open?

User Avatar
Flag of MEXICO

Hello, Authentication and account lifecycle issues can be difficult to spot because individual flows may work correctly while weaknesses appear in how they interact. OAuth, magic links, trip invitations, and account deletion deserve particular attention because they involve identity, permissions, and access to other users' data. I'd approach this as a focused, read-only security review of your TypeScript/Hono/PostgreSQL codebase at the agreed commit. I'd trace the complete authentication and invitation flows, check token generation and expiration, session handling, authorization boundaries, replay risks, and account deletion behavior, including related data and access revocation. You'll receive a prioritized report with severity, exact file and line references, realistic exploitation scenarios, and practical remediation recommendations. I'll respect the NDA, avoid production testing, and keep strictly within the agreed scope. Is the November 16 deadline fixed? I'd be happy to clarify the review scope before starting. Kind regards, Fernando

User Avatar
Flag of VIETNAM

Hello. I am Manh. “SECURITY REVIEW WITHOUT TOUCHING PRODUCTION” — You need a focused, evidence-based review of authentication, invitations, and account deletion, with clear findings your development team can act on. I would first map the sign-in flows across Apple OAuth, Google OAuth, and magic links, then trace how sessions, tokens, and account identities are validated. I would review trip invitations for authorization gaps, token misuse, and access-control issues, followed by account deletion for incomplete data removal, retained access, and related database records. I would work only from the agreed GitHub commit in a local environment, respecting the NDA and read-only scope. The report would include severity, affected files and line numbers, realistic impact, and recommended fixes. No production testing or code changes. Can you confirm whether the review should also cover session management and authorization checks across the related API endpoints?

User Avatar
Flag of INDIA

Magic links, Apple and Google sign-in, trip invites and account deletion all decide who gets into a trip, so I would review them by asking how someone could get in, or stay in, without being meant to. After the NDA and with the commit in hand, I would run the app locally on a scratch Postgres and read in this order: OAuth callbacks for state, nonce and redirect checks; magic-link tokens for expiry, single use and storage; invites for guessable or reusable tokens and membership checks on each Hono route; then deletion for leftover sessions, tokens and rows. The riskiest spot is how a provider login is matched to an existing email, since that is where account takeover tends to hide, so I would test it with crafted requests on my own machine only. Every finding comes with severity, file and line, what could go wrong, and a recommended fix, in one written report. Which rule does the app use today when a Google or Apple login arrives with an email that already has an account?

User Avatar
Flag of NETHERLANDS

Hello, Reviewing authentication flows in a TypeScript stack spanning React, Hono, and Postgres requires close attention to session token lifecycles, OAuth state parameter validation, and atomic transaction handling during account deletion. The main risk with magic-link sign-in and trip invitations lies in token reuse vulnerabilities, improper expiration enforcement, and broken object level authorization when guests accept shares. My review will trace these entry points directly in the codebase at your target commit to identify logic flaws and authorization bypasses, delivering structured findings with exact file paths, risk assessments, and targeted remediation steps. What specific mechanism handles session invalidation upon account deletion, and are cascading deletes enforced at the database layer? Have a nice day

User Avatar
Flag of UNITED STATES

Hello!, I am a Florida-based senior software engineer and I’d be a strong fit for this security review. The main risk here is not just bugs, but trust boundaries around sign-in, invite flows, account deletion, and Apple auth edge cases that can quietly expose accounts or allow privilege misuse. I’d handle it in phases: 1) map the auth and session flow end to end, 2) review TypeScript/Hono/React code for logic flaws, OAuth/session handling, CSRF, IDOR, invite abuse, and deletion bypasses, 3) test Postgres access patterns and permissions, 4) validate fixes with targeted re-testing and a concise report ranked by severity and impact. I’ve done security-focused reviews for SaaS apps, auth-heavy dashboards, and TypeScript/Node systems where the details matter more than the checklist. I pay close attention to the small things clients usually want caught before launch. A few questions: 1) Is Apple sign-in the only external auth provider, or are others in scope too? 2) Should I focus on code review only, or also do active testing against a staging environment? 3) Are account deletion and invite flows expected to meet any specific policy or audit requirement? Relevant work examples: - private SaaS invite/onboarding audit - React PWA auth hardening review - Node/Postgres permission model review - TypeScript admin portal security pass If you want, I can start with a risk-first checklist and then move straight into findings. -James

User Avatar
Flag of THAILAND

I’ve completed security reviews for TypeScript/Node web applications, including OAuth flows, passwordless links, invitation permissions, and deletion workflows. For this project, the key is tracing each identity and authorization boundary from React PWA through Hono to Postgres, because these flows can expose account access or data ownership gaps. I’ll review the named commit locally under the NDA and keep all work read-only. You’ll receive clear written findings by Monday, November 16, 2026, with severity, file and line references, realistic impact, and recommended fixes. I’ll verify OAuth state/redirect handling, magic-link expiry and replay controls, invite acceptance rules, and deletion behavior without touching production or publishing any code. Thanks, Kittipong

User Avatar
Flag of PAKISTAN

I can conduct a focused security review of your TypeScript, React PWA, Hono, and PostgreSQL codebase, covering OAuth, magic-link authentication, trip invitations, and account deletion. My experience includes Laravel SaaS technical reviews, API integrations, and application troubleshooting. I'll review the specified commit locally and deliver prioritized findings with severity, file/line references, potential impact, and practical fixes, without touching production. Are you ready to share the NDA and repository access details?

User Avatar
Flag of GERMANY

Hello, "Security review of web app sign-in, invites and account deletion" - the key is checking that identity, authorization, and account state stay consistent across every entry and exit path. I'll trace Apple and Google OAuth, magic-link sign-in, trip invitations, and account deletion through the relevant routes, session handling, and database operations, then document actionable findings with severity, file and line, realistic impact, and a recommended fix. I'll pay particular attention to expired or replayed invite links, account-linking edge cases, session revocation, and deletion paths that leave access behind. I'll review the named commit, run the code locally, and keep all testing off production, delivering the findings in one report. TypeScript, PostgreSQL, and OAuth are not listed among my confirmed core skills, so I will not overstate specialist depth in those areas. Does account deletion currently revoke all active sessions and OAuth-linked access, or is that behavior part of what you want reviewed? Looking forward to working with you. Beate

User Avatar
Flag of UNITED STATES

Hi there, The key requirement is a read-only security review of Apple/Google OAuth, magic-link authentication, trip invitations, and account deletion across the TypeScript/React PWA, Hono backend, and Postgres data layer, with precise severity, file/line references, impact, and recommended fixes. I have strong hands-on experience with Node.js and have solved similar problems involving authentication flows, authorization boundaries, account lifecycle logic, and database security. My approach would be to: * Review the existing code, architecture, logs, or current implementation. * Identify the root cause and determine what can be reused versus what needs to be changed. * Implement a clean, maintainable solution using Node.js, TypeScript, Hono, React, and Postgres analysis practices. * Test edge cases, reliability, performance, security, and integration behavior. * Deploy or integrate the fix without disrupting the existing system. I will work only against the approved commit and local environment, without production or live testing. Particular attention will go to token replay, OAuth account-linking decisions, invitation authorization, deletion completeness, and race conditions that could leave stale access or data. I prefer fixing the actual root cause rather than applying temporary patches, and I will keep the implementation simple, stable, and maintainable. I can start by reviewing the repository, commit, local setup, and authentication/data-flow boundaries, then deli

User Avatar
Flag of UNITED STATES

Hello, A security review of OAuth and magic-link flows usually uncovers one or two high-impact issues—token expiry, state validation, session fixation—that are easy to miss in code review but straightforward to patch once named. I've audited similar TypeScript stacks before, including a Hono API with Google OAuth where the state parameter wasn't being validated on callback, which would have let an attacker inject their own session. That one was caught and fixed in the same week. Reading through sign-in, invites, and account deletion on a named commit with local setup is the right scope; I'll trace the token lifecycle, check for timing attacks on magic links, and verify that invitation tokens can't be reused or guessed. My findings go into a written report with severity levels, exact file and line numbers, what the vulnerability enables, and a concrete fix for each one. You'll have it by Monday Nov 16 with enough detail that your team can patch without back-and-forth. For two weeks after, if anything in the report needs clarification, I'll answer questions at no extra cost. One quick question: are the magic-link tokens stored hashed in Postgres, or in plaintext? Thanks, Christian

User Avatar
Flag of PAKISTAN

The highest-risk areas are OAuth callback validation, magic-link replay, invitation authorization, and incomplete account deletion. I'd review the React/TypeScript, Hono, and PostgreSQL code at the specified commit, checking authentication, session handling, access controls, and data cleanup. I'll work under NDA, without production access or code changes, and deliver a prioritized report with severity, file/line references, impact, and actionable fixes by November 16.

User Avatar
Flag of MOLDOVA, REPUBLIC OF

Hello. I understand the importance of ensuring the security of your web app, especially when it comes to sensitive functionalities like sign-ins and account deletions. A thorough review of your Apple/Google OAuth integration and magic-link sign-ins is crucial to identify potential vulnerabilities. One aspect that stands out is the need for a detailed report that not only identifies issues but also provides actionable recommendations. I have previously conducted security assessments for applications built with similar tech stacks, specifically focusing on OAuth implementations and user authentication flows. By addressing these security concerns effectively, you can significantly enhance user trust and protect sensitive data. What specific security standards or frameworks do you prefer for this review? Thanks, Artiom.

User Avatar
Flag of SERBIA

I can conduct a focused security review of your TypeScript/React PWA, Hono backend, and Postgres workflows after the mutual NDA and named-commit access are in place. The review will cover Apple and Google OAuth, magic-link authentication, trip invitations, authorization boundaries, account deletion, token/session handling, identity linking, replay risks, enumeration, data retention, and relevant error-handling paths. I’ll run the application locally where useful, without production or live testing, and keep the assessment limited to the agreed commit. You’ll receive clear written findings organized by severity, including precise file and line references, realistic impact scenarios, and practical recommended fixes. I’ll also distinguish confirmed vulnerabilities from defense-in-depth observations so the results are actionable before the Monday, November 16, 2026 deadline. I’m comfortable working under NDA, using read-only GitHub access, and not publishing or sharing any project code or findings.

User Avatar
Flag of PAKISTAN

My TypeScript, Node.js, PostgreSQL and Web Security skills align directly with reviewing your Hono server and authentication flows. As a full-stack developer, I understand how frontend behavior, API logic, database access and account lifecycle decisions connect—particularly where OAuth, magic links, invitations and deletion can expose authorization or data-handling weaknesses. I can work from the specified read-only commit and keep the review strictly within the agreed scope, without production or live testing. My findings will be written for practical use, with severity, precise file/line references, the potential impact, and a recommended fix. My PostgreSQL and API experience also supports careful review of invite permissions, user ownership, session/token handling and account-deletion effects across related records. I am ready to complete a focused, code-based security review and deliver clear findings by Monday, November 16, 2026. Choose me for a disciplined review of these sign-in and account-management paths.

内容来自 Freelancer News,版权归原作者所有。

阅读原文 ↗

把喜欢的内容,留在你的新标签页。

打开我的订阅