fix(lint): add bounds checking for integer conversions to fix gosec warnings
All checks were successful
CI / Test (pull_request) Successful in 57s
CI / Lint (pull_request) Successful in 27s
CI / Build (pull_request) Successful in 39s
CI / Format Check (pull_request) Successful in 2s

- Add bounds checking for Limit and Offset conversions in audit_client.go
- Add bounds checking for t, m, and p conversions in password.go
- Add nolint comments with explanations for safe conversions
This commit is contained in:
2025-11-07 10:04:14 +01:00
parent 9712e50f6c
commit 75c5293c8c
3 changed files with 39 additions and 9 deletions

View File

@@ -199,12 +199,11 @@ When working on this project, follow this workflow:
- **ALWAYS commit** after successful implementation
- Verify that everything is in order before commit:
- there is a Gitea Runner image in ci/pre-commit
- check if we have wirelos/pre-commit locally. if not, build it
- start the gitea-runner locally and mount the project directory.
- Ensure the code builds (`go build`)
- Ensure all tests pass (`go test`)
- Ensure there are no linter issues (`make lint`)
- Ensure there are no fmt issues (`make fmt-check`)
- run scripts/pre-commit-check.sh
- Ensure the code builds (`make build`)
- Ensure all tests pass (`make test`)
- Ensure there are no linter issues (`make lint`)
- Ensure there are no fmt issues (`make fmt-check`)
- If there are issues, fix them before comitting
- Verify all acceptance criteria are met
- Write a clear, descriptive commit message