Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

[infra/deploy] ci: Harden GitHub Actions #9

Conversation

step-security-bot
Copy link

@step-security-bot step-security-bot commented Jan 22, 2025

Summary

I'm onboarding our new CI/CD security tool: HardenRunner. A few lines are added to certain workflow files to enable the scanners.

It will scan for anomalies on the CI/CD side without making any changes (unless manually requested).

fixes https://github.com/neondatabase/cloud/issues/21253

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
@github-advanced-security
Copy link

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

@areyou1or0 areyou1or0 changed the title [StepSecurity] Apply security best practices [infra/deploy] ci: Harden GitHub Actions Jan 22, 2025
fixing this error message:

  level=error msg="[linters_context] gocritic: load embedded ruleguard rules: rules/rules.go:13: can't load fmt: setting an explicit GOROOT can fix this problem."
@areyou1or0
Copy link

closing this one, installation is not working - will troubleshoot later.

@areyou1or0 areyou1or0 closed this Jan 23, 2025
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants