ashrafee-dev / ashrafee-dev/scamshield-api
Constrain risk-assessment certainty
Open
Beginner friendly
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 riskAssessment model accepts any integer for certainty, even though the API contract and model prompt require a value from 0 to 100.
Acceptance criteria
- Enforce an inclusive 0–100 range in the Pydantic response model.
- Add tests for the lower bound, upper bound, and invalid values.
- Keep valid existing responses unchanged.
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
Locate the riskAssessment Pydantic response model and the existing tests for its certainty field. Add coverage for 0, 100, and out-of-range values, then run the relevant test suite; done means the inclusive 0–100 constraint is enforced while valid existing responses remain unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 78/100