ashrafee-dev / ashrafee-dev/scamshield-api
Fail clearly when DEEPSEEK_API_KEY is missing
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 application can start with no DEEPSEEK_API_KEY, then fail later during an analysis request with an unclear upstream error.
Acceptance criteria
- Validate the required key during startup or configuration loading.
- Provide a clear, secret-safe error message.
- Add a test for missing configuration without making a real API call.
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 by locating the configuration-loading and FastAPI startup entry points, then inspect nearby tests for configuration or startup behavior. Add a test that runs without a real API call and verifies a clear, secret-safe failure when DEEPSEEK_API_KEY is absent; done means the application rejects missing configuration early.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- fastapi, python
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 74/100