Run pgspot in CI
Open
developer experience
- Dominant language
- C++
- Stars
- 3.2k
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
### Description
Let's keep our extension scripts secure by listening to `pgspot`. It seems easier to do that if CI complains when we add insecure things, than after the fact during each release. It's really quick tool to run, so I think it should be fine CI duration wise.
Related to #343
Contributor guide
Research direction
Start by reading the repository's CI configuration and related issue #343 to understand the intended pgspot checks. Verify how pgspot should scan the extension scripts in CI and confirm that insecure additions cause CI to fail without an unacceptable duration increase.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql
- Domain
- ci-cd, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100