-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add scanning for misconfigurations #248
Conversation
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. |
node-red:3.0.2-main-linux-amd64 scan results1 files ±0 4 suites ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit 7602b20. ± Comparison against base commit 721173e. This pull request removes 6 tests.
|
node-red:3.0.2-main-linux-arm64 scan results1 files ±0 4 suites ±0 0s ⏱️ ±0s For more details on these failures, see this check. Results for commit 7602b20. ± Comparison against base commit 721173e. This pull request removes 6 tests.
|
Looks like the re-spin of the 3.0.2 removed all the OS level CVEs (only npm left by the look of it) |
Description
Add step in the pipeline to validate helm chart against best practices and misconfigurations.
Related Issue(s)
#213
Checklist
flowforge.yml
?FlowFuse/helm
to update ConfigMap TemplateFlowFuse/CloudProject
to update values for Staging/ProductionLabels
backport
labelarea:migration
label