Repository navigation
build(deps): bump trufflesecurity/trufflehog from 3.99.3 to 3.99.8 - #358
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [trufflesecurity/trufflehog](https://github.com/trufflesecurity/trufflehog) from 3.99.3 to 3.99.8. - [Release notes](https://github.com/trufflesecurity/trufflehog/releases) - [Commits](trufflesecurity/trufflehog@e63326d...ea68ca0) --- updated-dependencies: - dependency-name: trufflesecurity/trufflehog dependency-version: 3.99.8 dependency-type: direct:production update-type: version-update:semver-patch ... 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: blocked before merge. What this changesThis PR updates the pinned TruffleHog action reference from v3.99.3 to v3.99.8. Example: A pull request runs the secret-scanning workflow.
Review scores
ProductKind: Maintenance · Worth it: No · Fix scope: Complete Merge readiness⛔ Blocked before merge - 1 item remains This PR introduces no identified defect, but delivers no scanner upgrade or executable action change; a maintainer previously closed the equivalent wrapper-only update, and repository policy does not authorize automatic closure here. Priority: P3 Decision needed
Before merge
FindingsNone. Agent review detailsHow this fits togetherGitHub Actions resolves the changed commit range and passes it to TruffleHog, which fails the security gate when verified secrets are found. flowchart TD
A[Push or pull request] --> B[Checkout repository history]
B --> C[Resolve scan range]
C --> D[Pinned TruffleHog action]
D --> E[Scanner image 3.99.4]
E --> F[Verified secret gate]
Technical reviewBest possible solution: Follow the prior maintainer decision and reserve scanner upgrades for a focused change that updates and qualifies the explicit runtime artifact. Do we have a high-confidence way to reproduce the issue? No product bug is asserted; source inspection establishes that the proposed reference change leaves executed scanner behavior unchanged. Is this the best way to solve the issue? The patch correctly refreshes the wrapper reference, but cannot deliver the advertised upstream scanner improvements while the runtime remains pinned to 3.99.4. AGENTS.md: found but not applied because it conflicted with ClawSweeper's review contract. Codex review notes: model internal, reasoning medium; reviewed against b39ecf743295. Provenance checked
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 5, 2026, 1:57 PM ET / 18:57 UTC. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps trufflesecurity/trufflehog from 3.99.3 to 3.99.8.
Release notes
Sourced from trufflesecurity/trufflehog's releases.
... (truncated)
Commits
ea68ca0Verify BoxOauth credentials only when Box issues a token for a subject (#5498)7238e0eClean up GitLab source logging for per-source debug (#5485)5a3176fUpdate module github.com/mattn/go-isatty to v0.0.24 (#5366)a74daf6Update module github.com/jlaffaye/ftp to v0.2.4 (#5365)1641840Update module github.com/go-git/go-git/v5 to v5.19.3 (#5480)ee5d0d2Cap 7z LZMA and LZMA2 dictionary sizes and keep scanning past refused entries...421026aRecover from detector panics in the verification overlap worker (#5495)6973459Close Couchbase clusters after verification and honor the context (#5489)87adc84Add source fields to Init logs in single-source CLI commands (#5466)020634eClean up Docker source logging for per-source debug (#5494)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 this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)