pgadmin-org / pgadmin-org/pgadmin4
pgAdmin: Content Security Policy
Open
Nobody has claimed this yet.
Bug
- Dominant language
- Python
- Stars
- 3.8k
- Forks
- 891
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 8
Description
Let's work to remove the 'unsafe-inline' and 'unsafe-eval' from the CSP.
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
The issue names no files, tests, or entry points. Start by locating the pgAdmin Content Security Policy configuration and auditing the sources of inline code and evaluated code; done means removing both unsafe directives without breaking the application.
Written by the indexing model from the issue text.
Assessment
- Domain
- security, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100