You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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>
The generic test patterns (63 directory names, 23 file globs) were applied
to TruffleHog as well as OpenGrep. Excluding test code from SAST is sound,
but a credential committed to a test file is as live as one anywhere else,
and trufflehog_exclude_dir stops the file being opened -- making it a
permanent blind spot for every future secret in those paths.
Measured across all 120 repos: dropping the test patterns surfaces 77
additional detections in 20 files across 7 repos, and all 77 are false
positives -- 43 are UUIDs and random column values in CSV migration
fixtures, the rest one generated ECDSA test key pasted into nine files,
localhost postgres DSNs, and test JWTs. Those 20 files are now listed
individually, so every other test file is scanned for secrets.
.semgrepignore is unchanged; SAST keeps its test exclusions.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The job inherited GitHub's 360-minute default. Measured scan work across
all 120 repos is 30.3s at the slowest and 8.3s at the median, so 30
minutes leaves roughly sixty times the observed worst case while still
failing a hung run in minutes rather than hours.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
The reason will be displayed to describe this comment to others. Learn more.
Copilot review overview
🔵 Needs a closer look
Scanner and upload failures can currently produce a successful workflow result.
Review effort: Balanced Findings: None
Previously missed (1)
In code that hasn't changed since last review
Fail the job when scanner connectors or result upload fail
.github/workflows/socket-basics.yml:49
This direct invocation trusts the scanner's exit status, but the pinned scanner runs connectors with fail_fast: false, catches Socket API submission failures, and then exits based only on the high/critical finding count. An OpenGrep, TruffleHog, Trivy, or dashboard-upload failure can therefore leave this weekly job green with partial or missing results. Gate success on completion of every enabled connector and a successful full-scan upload, or pin a scanner release that fails closed for those errors.
The Protocol 30 merge added src/rust/soroban/p29 and p30 as submodules.
repo_ignores() reads .gitmodules, so regenerating .semgrepignore picks
them up alongside p21-p28; without this they would be scanned as
first-party code once checked out.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Comment incorrectly claims trivy_disabled_rules is unsupported
.trivyignore:4
This explanation is incorrect for the configured Socket Basics generation: upstream exposes trivy_disabled_rules as a JSON configuration key (it is documented and present as far back as v3.0.0). Keeping the comment as written will mislead future tuning work into maintaining a separate ignore mechanism unnecessarily.
# Trivy reads this file from the working directory. socket-basics has no config
# key that can disable a Trivy rule, so this is the only lever.
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
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.
More info: https://stellarorg.atlassian.net/wiki/spaces/SCRT/pages/5901680652/Socket+Basics+Integration+Guide