Kinda broken.
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
I think this is kinda very flawed.
First, you can do this:
- Login to site A
- Site A gets code from site B
- User posts code
- Site A now has control over the account on site B
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
No file, test, or entry point is named. Start by tracing the server-side login and code-handling flow described in the issue, then document the affected trust boundary and a reproducible test that demonstrates the account-control problem; done requires an agreed security fix and verification that the flow no longer permits it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- express, javascript
- Domain
- authentication, backend, security
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 18/100