Skip to content

build(deps): bump trufflesecurity/trufflehog from 3.99.3 to 3.99.8 - #205

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/trufflesecurity/trufflehog-3.99.8
Closed

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/github_actions/trufflesecurity/trufflehog-3.99.8

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 6, 2026

Copy link
Copy Markdown
Contributor

Bumps trufflesecurity/trufflehog from 3.99.3 to 3.99.8.

Release notes

Sourced from trufflesecurity/trufflehog's releases.

v3.99.8

What's Changed

New Contributors

Full Changelog: trufflesecurity/trufflehog@v3.99.7...v3.99.8

v3.99.7

What's Changed

New Contributors

Full Changelog: trufflesecurity/trufflehog@v3.99.6...v3.99.7

v3.99.6

v3.99.5 was tagged but never published because its release build failed. v3.99.6 supersedes it and includes all of the changes below.

What's Changed

... (truncated)

Commits
  • ea68ca0 Verify BoxOauth credentials only when Box issues a token for a subject (#5498)
  • 7238e0e Clean up GitLab source logging for per-source debug (#5485)
  • 5a3176f Update module github.com/mattn/go-isatty to v0.0.24 (#5366)
  • a74daf6 Update module github.com/jlaffaye/ftp to v0.2.4 (#5365)
  • 1641840 Update module github.com/go-git/go-git/v5 to v5.19.3 (#5480)
  • ee5d0d2 Cap 7z LZMA and LZMA2 dictionary sizes and keep scanning past refused entries...
  • 421026a Recover from detector panics in the verification overlap worker (#5495)
  • 6973459 Close Couchbase clusters after verification and honor the context (#5489)
  • 87adc84 Add source fields to Init logs in single-source CLI commands (#5466)
  • 020634e Clean up Docker source logging for per-source debug (#5494)
  • Additional commits viewable in compare view

Dependabot compatibility score

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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

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>
@dependabot
dependabot Bot requested a review from a team as a code owner November 6, 2026 07:23
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code labels Nov 6, 2026
@clawsweeper

clawsweeper Bot commented Nov 6, 2026 •

Copy link
Copy Markdown

🦞👀
ClawSweeper picked this up.

Pull request received. I will update this pull request when review starts.

ClawSweeper review complete

ClawSweeper finished reviewing this revision. The review result is being finalized.

View the workflow run.

@clawsweeper clawsweeper Bot added P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited. labels Nov 6, 2026
@clawsweeper

clawsweeper Bot commented Nov 6, 2026

Copy link
Copy Markdown

Codex review: blocked before merge.

What this changes

This PR updates the pinned TruffleHog action reference from v3.99.3 to v3.99.8.

Example: GitHub Actions scans a pull request for verified secrets.

  • Before: The v3.99.3 action wrapper runs scanner image 3.99.4.
  • After: The v3.99.8 action wrapper runs the identical action code and scanner image 3.99.4.

Review scores

Measure Result What it means
Overall readiness 🦐 gold shrimp (3/6) Mechanically correct and narrowly scoped, with no demonstrated maintenance benefit under the recorded precedent.
Proof confidence 🌊 off-meta tidepool Not applicable: This bot-authored reference update preserves the complete executable action and scanner input; exact-head workflow metadata reports successful execution, while detailed logs were inaccessible through the artifact-host allowlist.
Patch quality 🐚 platinum hermit (4/6) No actionable review findings were identified.

Product

Kind: Maintenance · Worth it: No
User problem: No concrete user-visible problem is established by this wrapper-only update.
Reason: The action code is byte-identical and scanner 3.99.4 remains selected; a maintainer previously rejected the same kind of update for lacking operational uplift.

Merge readiness

⛔ Blocked before merge - 1 item remains

This PR changes no executed action code or scanner version and establishes no operational benefit; repository policy reserves this cleanup decision for a maintainer.

Priority: P3
Reviewed head: e93e9ba9336cfd32e251a16c1df1d97f6a28399c
Owner decision: Required. See Decision needed.

Decision needed

  • Question: Should this behaviorally unchanged wrapper update be declined under the prior closeout precedent?
  • Recommendation: Close manually: Apply the prior decision because the executed wrapper and selected scanner remain unchanged.
  • Why: The analogous update was explicitly declined, but repository policy permits automated closure only for changes certainly implemented on main.

Before merge

  • Product: not worth merging - The action code is byte-identical and scanner 3.99.4 remains selected; a maintainer previously rejected the same kind of update for lacking operational uplift.

Findings

None.

Agent review details

How this fits together

The secret-scanning workflow passes a Git commit range to the upstream composite action, which runs the selected scanner container and fails when verified secrets are found.

flowchart LR
  A[Push or pull request] --> B[Resolve commit range]
  B --> C[Pinned TruffleHog action]
  C --> D[Scanner image 3.99.4]
  D --> E[Secret scan result]
  E --> F[Workflow gate]
Loading

Technical review

Best possible solution:

A maintainer should apply the prior wrapper-only closeout decision, with any scanner upgrade handled separately through explicit artifact qualification.

Do we have a high-confidence way to reproduce the issue?

This is dependency maintenance rather than a reported bug; source and upstream blob identity establish its behavioral scope.

Is this the best way to solve the issue?

The one-line patch is mechanically correct, but it delivers none of the newer scanner fixes and repeats an update previously declined by a maintainer.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning medium; reviewed against 805fe5e2c3af.

Provenance checked

Testing

Proof path: none.

Security

None.

Evidence

What I checked:

Likely related people:

  • Vincent Koc: Raw commit ae16f4d adds .github/workflows/secret-scan.yml:13 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: ae16f4d2a0bd; files: .github/workflows/secret-scan.yml)
  • Josh Avant: Raw commit b7cf3a6 adds .github/workflows/secret-scan.yml:57 relative to its recorded parents. This identifies author metadata, not feature responsibility or a PR merger. (role: source-line author; confidence: high; commits: b7cf3a6de3dc; files: .github/workflows/secret-scan.yml)

Preflight source

Source unknown. Source comparison at the observed PR snapshot only. Completion is self-reported; body, policy, tests, execution, and report bytes are not verified.

Labels

Label changes:

  • add P3: Routine action-reference maintenance with identical executed code and unchanged scanner selection.
  • add rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Label justifications:

  • P3: Routine action-reference maintenance with identical executed code and unchanged scanner selection.
  • rating: 🦐 gold shrimp: Overall readiness is 🦐 gold shrimp; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.

Rating scale

6/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.

Workflow

ClawSweeper edits this one comment on every review. Comment @clawsweeper re-review for a fresh review only. Repair and merge execution lanes are retired.

Reviewed November 6, 2026, 2:36 AM ET / 07:36 UTC.

@vincentkoc vincentkoc closed this Nov 9, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file github_actions Pull requests that update GitHub Actions code P3 Low-risk cleanup, docs, polish, ergonomics, or speculative feature. rating: 🦐 gold shrimp Decent PR readiness signal, but merge confidence is limited.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant