Repository navigation
ci: security scanning, with the findings read and justified - #12
Merged
Merged
Conversation
marcos-mendez
force-pushed
the
ci/security-scan
branch
from
October 7, 2026 17:57
9020deb to
e8cb7dd
Compare
Calls security-scan.yml of keel-linux/.github (gitleaks, bandit, semgrep, shellcheck on hosted runners, no secrets) on pull requests, pushes to master and by hand. Not a required check. Baseline from a scan of master, none a risk. B103 and semgrep's insecure-file-permissions: 0755 on scripts that must run in the build chroot. B324 and semgrep's MD5 rule: md5 keys a dict of comments, and fills the MD5sum field of a local Packages index beside SHA256. Plus six shellcheck warnings in share/initctl.dummy. gitleaks finds nothing.
marcos-mendez
force-pushed
the
ci/security-scan
branch
from
October 7, 2026 18:17
e8cb7dd to
0f61589
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Calls security-scan.yml of keel-linux/.github (gitleaks, bandit,
semgrep, shellcheck on hosted runners, no secrets) on pull requests,
pushes to master and by hand. Not a required check.
Baseline from a scan of master, none a risk. B103 and semgrep's
insecure-file-permissions: 0755 on scripts that must run in the build
chroot. B324 and semgrep's MD5 rule: md5 keys a dict of comments, and
fills the MD5sum field of a local Packages index beside SHA256. Plus six
shellcheck warnings in share/initctl.dummy. gitleaks finds nothing.