Repository navigation
build(deps): bump trufflesecurity/trufflehog from 3.99.8 to 3.99.9 in the github-actions group - #259
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps the github-actions group with 1 update: [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog). Updates `trufflesecurity/trufflehog` from 3.99.8 to 3.99.9 - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](trufflesecurity/trufflehog@ea68ca0...3bd2b58) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.99.9 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: github-actions ... Signed-off-by: dependabot[bot] <support@github.com>
|
🦞👀 Pull request received. I will update this pull request when review starts. ClawSweeper review completeClawSweeper finished reviewing this revision. The review result is being finalized. |
|
Codex review: needs maintainer review before merge. What this changesUpdates the TruffleHog GitHub Action source pin from v3.99.8 to v3.99.9 while retaining scanner image version 3.99.7. Example: A pull request triggers secret scanning.
Review scores
ProductKind: Maintenance · Worth it: Yes · Fix scope: Complete Merge readiness✅ Ready for maintainer review This PR is a clean dependency-pin refresh that is absent from main; no introduced defect or merge blocker was found. Priority: P3 Before mergeNone. FindingsNone. Agent review detailsHow this fits togetherThe GitHub Actions security workflow passes repository paths and commit ranges to TruffleHog, which scans for verified secrets and reports a CI result. flowchart LR
A[Push or pull request] --> B[Repository checkout]
B --> C[Resolve commit range]
C --> D[Pinned TruffleHog action]
D --> E[Scanner image 3.99.7]
E --> F[Secret scan result]
Technical reviewBest possible solution: Land the verified action-pin refresh while preserving the independently selected scanner runtime. Do we have a high-confidence way to reproduce the issue? No product bug is claimed; source inspection verifies the pin update and unchanged scanner execution. Is this the best way to solve the issue? The single-line update follows the existing immutable action-pin pattern and preserves the established runtime contract. AGENTS.md: found and applied where relevant. Codex review notes: model internal, reasoning medium; reviewed against d0bca5e533cf. Provenance checked
TestingProof path: none. SecurityNone. EvidenceWhat I checked:
Likely related people:
Preflight sourceSource unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified. LabelsLabel changes:
Label justifications:
Rating scale6/6 🦀 challenger crab · 5/6 🦞 diamond lobster · 4/6 🐚 platinum hermit · 3/6 🦐 gold shrimp · 2/6 🦪 silver shellfish · 1/6 🧂 unranked krab. Overall follows the weaker of proof and patch quality; ✨ marks media proof (a screenshot, video, or linked artifact) that directly shows the changed behavior. WorkflowClawSweeper edits this one comment on every review. Comment Reviewed November 16, 2026, 12:20 PM ET / 17:20 UTC. |
Bumps the github-actions group with 1 update: trufflesecurity/trufflehog.
Updates
trufflesecurity/trufflehogfrom 3.99.8 to 3.99.9Release notes
Sourced from trufflesecurity/trufflehog's releases.
Commits
3bd2b58Add SOURCE_TYPE_GENERIC source type (#5553)256d9d4Report Datadog resources as unbounded instead of permission-less bindings (#5...ef3c2c5Fix GitHub GraphQL comment scan retries and paging (#5548)f8ad753Clean up Syslog source logging for per-source debug (#5538)0344195Update module pault.ag/go/debian to v0.21.3 (#5546)2c07884Update module golang.org/x/crypto to v0.59.0 [SECURITY] (#5544)1887667feat(detectors): add Serval API key detector (#5528)221b979Clean up Elasticsearch source logging for per-source debug (#5521)5dce9d4Clean up Hugging Face source logging for per-source debug (#5523)47325abClean up CircleCI and Travis CI logging, share API log hooks (#5524)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions