Potential fix for code scanning alert no. 67: Workflow does not contain permissions

[Dargon789]

Potential fix for https://github.com/Dargon789/Ethereumjs-Webserver/security/code-scanning/67

To fix this issue, add a permissions block with least privilege at the root level of the workflow (just after the name: or the on: block), or scoped to the test-tx job if different jobs have distinct needs. For this workflow, since it primarily checks out code, installs dependencies, runs lint, coverage, and pushes coverage data (to Codecov, not back to GitHub), it only requires read access to repository contents. Thus, set permissions: contents: read at the workflow level, which restricts the GITHUB_TOKEN in all jobs unless overridden.

Edit .github/workflows/tx-build.yml:

• Insert the following under the name: Tx line (before on:):

  permissions:
    contents: read

No method, import, or other code is needed; this is a pure configuration change.

Suggested fixes powered by Copilot Autofix. Review carefully before merging.

Summary by Sourcery

CI:

• Add permissions.contents: read at the root of .github/workflows/tx-build.yml to grant only read access to repository contents

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
ethereumjs-webserver-omeq	Ready	Preview	Comment	Oct 24, 2025 0:33am
workspace	Ready	Preview	Comment	Oct 24, 2025 0:33am

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR updates the Tx GitHub Actions workflow to enforce least-privilege by adding a permissions block that restricts the GITHUB_TOKEN to read-only repository contents, resolving the code-scanning alert.

File-Level Changes

Change	Details	Files
Enforce least-privilege permissions at the workflow level	Insert permissions: block immediately after the workflow name Set contents: read under permissions	.github/workflows/tx-build.yml

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[snyk-io]

✅ Snyk checks have passed. No issues have been found so far.

Status	Scanner	Critical	High	Medium	Low	Total (0)
✅	Open Source Security	0	0	0	0	0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.13%. Comparing base (ff99c86) to head (c4fd07e).
⚠️ Report is 9 commits behind head on master.

Additional details and impacted files

Flag	Coverage Δ
blockchain	91.61% <ø> (?)
client	?
common	98.43% <ø> (?)
devp2p	81.95% <ø> (?)
evm	74.05% <ø> (?)
genesis	99.98% <ø> (?)
trie	89.28% <ø> (?)
wallet	?

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}