Repository navigation
Add the org security scan workflow (Semgrep, Trivy, Gitleaks) - #116
Merged
Merged
Conversation
b-Tomas
approved these changes
Oct 30, 2026
This was referenced Oct 30, 2026
Add the org security scan workflow (Semgrep, Trivy, Gitleaks)
inorbit-ai/inorbit-connector-python#99
Merged
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
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.
Runs the shared security scan from inorbit-ai/.github on pull requests, on pushes to
main, weekly (Mondays 07:00 UTC) and on demand: Semgrep (SAST), Trivy (dependencies) and Gitleaks (secrets, redacted). Report-only: findings never fail the build; counts are in the job summary and the full reports in thesecurity-reportsartifact.Part of SOC 2 T-18.1 (scheduled code scans on every production repository).