Repository navigation
Add Socket Basics security scanning workflow - #3014
Conversation
8d447c6 to
082d27e
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Unresolved critical and moderate security-scan configuration and workflow issues require changes before approval.
Review effort: Lite
Findings: 1
Open (2)
What changed in this PR
Adds a scheduled and manually triggered Socket Basics security scanning workflow.
Changes:
- Configures SAST and secret scanning.
- Adds Semgrep exclusion rules.
- Adds a pinned Docker-based GitHub Actions workflow.
| File | Summary |
|---|---|
.socket-basics.json |
Configures scanner features and exclusions; several security coverage issues require changes. |
.semgrepignore |
Defines SAST exclusions. |
.github/workflows/socket-basics.yml |
Runs the scheduled/manual scan; completion handling has a critical issue. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
082d27e to
c5e9571
Compare
c5e9571 to
b6b612b
Compare
b6b612b to
aa4e3f7
Compare
aa4e3f7 to
9c4ce4b
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Unresolved findings affect scan enforcement, result reporting, and security coverage.
Review effort: Lite
Findings: 2
Open (6)
Propagate scanner failures instead of exiting successfully · New Prevent GitHub token exposure in third-party scanner container Preserve non-zero scanner exit statuses Do not exclude tests from TruffleHog secret scanning Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
9c4ce4b to
3b80b4c
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Fix scanner failure-status handling and avoid globally disabling sensitive-data logging detection.
Review effort: Lite
Findings: 1
Open (6)
Propagate scanner failures instead of exiting successfully Global sensitive-data logging rule disablement hides future leaks · New Preserve non-zero scanner exit statuses Do not exclude tests from TruffleHog secret scanning Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
Resolved since last review (1)
3b80b4c to
78e1c3d
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Moderate issues could mask security findings or scanner failures.
Review effort: Lite
Findings: 1
Open (7)
Propagate scanner failures instead of exiting successfully Disabled logging-secret detection permits sensitive data leaks · New Global sensitive-data logging rule disablement hides future leaks Preserve non-zero scanner exit statuses Do not exclude tests from TruffleHog secret scanning Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
78e1c3d to
794d050
Compare
794d050 to
cfd729e
Compare
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
Security scan suppressions and exclusions are broader than recommended.
Review effort: Lite
Findings: 6
Open (6)
Narrow hardcoded-secret suppressions to specific known false positives · New Disabled logging-secret detection permits sensitive data leaks Global sensitive-data logging rule disablement hides future leaks Do not exclude tests from TruffleHog secret scanning Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
Remove the global sensitive-data-in-logs suppression and use path-specific overrides for verified false positives.
Review effort: Lite
Findings: 5
Open (5)
Narrow hardcoded-secret suppressions to specific known false positives Disabled logging-secret detection permits sensitive data leaks Global sensitive-data logging rule disablement hides future leaks Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
Resolved since last review (1)
Runs SAST through OpenGrep, secret scanning through TruffleHog, and
Dockerfile misconfiguration scanning through Trivy, submitting results
to Socket.dev.
.github/workflows/socket-basics.yml scheduled weekly + manual dispatch
.socket-basics.json scanner configuration
.semgrepignore SAST path exclusions
.trivyignore Dockerfile lint rules with no
security dimension (only present
where the repo has a Dockerfile)
Separate from socket-scan.yml, which covers dependency CVEs and Tier 1
reachability.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot review overview
🔵 Needs a closer look
Broad scanner suppressions can hide future secrets, credentials, and sensitive-data logging.
Review effort: Lite
Findings: 5
Open (5)
Narrow hardcoded-secret suppressions to specific known false positives Disabled logging-secret detection permits sensitive data leaks Global sensitive-data logging rule disablement hides future leaks Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
|
There was a problem hiding this comment.
🟢 Approval recommended
All reviewed changes are covered and no unresolved blocking issues were identified.
0 open findings
5 resolved since last review
Narrow hardcoded-secret suppressions to specific known false positives Disabled logging-secret detection permits sensitive data leaks Global sensitive-data logging rule disablement hides future leaks Global suppression hides sensitive-data logging in JavaScript Trivy vulnerability scanning is disabled
🧠 Review effort: Lite
Give feedback about Copilot approvals in this survey to enter a drawing for a $150 gift card.


More info: https://stellarorg.atlassian.net/wiki/spaces/SCRT/pages/5901680652/Socket+Basics+Integration+Guide