learningequality / learningequality/studio
Ensure DB utilities used for development are only used for development
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 191
- Forks
- 307
- Avg merge
- 5d 6h
- Merged PRs (30d)
- 10
Description
❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.
Description
We have code that's used for development purposes only, and it would be good to better distinguish the code, like that in the code scanning report, is clearly only for development environments.
References
Tracking issue for:
Contributor guide
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 with the linked code-scanning report at security/code-scanning/6 and identify which development-only DB utilities it flags. Trace where those utilities are used and determine how the project distinguishes development environments. Done means the development-only code is clearly separated from non-development use and the reported finding is addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- database, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100