ashrafee-dev / ashrafee-dev/scamshield-api
Use the email sender in scam analysis
Open
Nobody has claimed this yet.
good first issue
- Dominant language
- Python
- Stars
- 3
- Forks
- 10
- Avg merge
- 14h 44m
- Merged PRs (30d)
- 9
Description
Problem
The email request model collects sender, but /email currently sends only body to the assessment service.
Acceptance criteria
- Decide whether sender information should contribute to analysis.
- If it should, pass it through using the existing privacy filtering path.
- Add a test proving the selected behavior and update the API documentation.
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
Start at the email request model and the /email endpoint, then trace the assessment service and existing privacy filtering path. Decide whether sender data should affect analysis, add a test proving that behavior, and update the API documentation to match.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100