chore: independent security review

Open
#424 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
8/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript

Research direction

The issue names no files, tests or entry points; its scope is auth flows, tokens, sessions, OTP, WebAuthn, the OIDC provider and crypto. Commissioning an independent review is maintainer work, not a newcomer code change. Done means a completed external review whose findings are fixed or tracked publicly. A newcomer should not start here.

Written by the indexing model from the issue text.

Description

P1 secure v1.0

Why

A citable outside review is the strongest evidence for the most-secure promise.

What

  • Scope: auth flows, tokens, sessions, OTP, WebAuthn, OIDC provider, crypto
  • Publish the report summary and fixes

Done when

A review is completed and its findings are fixed or tracked publicly.

Dominant language
TypeScript
Stars
2
Forks
2
Avg merge
11h 40m
Merged PRs (30d)
104

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fells-code/seamless-auth-api

All issues in fells-code/seamless-auth-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.