Repository navigation
ci: add secret detection - #10
Merged
Merged
Conversation
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.
Summary
Add Gitleaks secret detection to the Offlink GitHub Actions CI workflow.
What Changed
Why
Introduce a lightweight AppSec security gate into the Offlink learning project.
The goal is to automatically detect accidentally committed secrets such as:
CI Flow
Checkout
→ Gitleaks Secret Detection
→ Flutter Setup
→ Dependencies
→ Format
→ Analyze
→ Tests
→ Android Build
Testing
Scope
This PR intentionally adds only secret detection.
Dependency vulnerability scanning, SAST, SBOM, DAST, and other advanced AppSec checks will be introduced separately as future learning steps.
Risk
No application runtime behavior is changed.
Only the CI pipeline is updated.