[StepSecurity] Apply security best practices by step-security-bot · Pull Request #116 · jshttp/http-errors · GitHub
Skip to content

[StepSecurity] Apply security best practices#116

Merged
UlisesGascon merged 2 commits into
jshttp:masterfrom
step-security-bot:chore/GHA-181738-stepsecurity-remediation
Jun 2, 2025
Merged

[StepSecurity] Apply security best practices#116
UlisesGascon merged 2 commits into
jshttp:masterfrom
step-security-bot:chore/GHA-181738-stepsecurity-remediation

Conversation

@step-security-bot

@step-security-bot step-security-bot commented May 18, 2025

Copy link
Copy Markdown
Contributor

Related expressjs/security-wg#2

Summary

This pull request is created by StepSecurity at the request of @UlisesGascon. Please merge the Pull Request to incorporate the requested changes. Please tag @UlisesGascon on your message if you have any questions related to the PR.

Security Fixes

Least Privileged GitHub Actions Token Permissions

The GITHUB_TOKEN is an automatically generated secret to make authenticated calls to the GitHub API. GitHub recommends setting minimum token permissions for the GITHUB_TOKEN.

Pinned Dependencies

GitHub Action tags and Docker tags are mutable. This poses a security risk. GitHub's Security Hardening guide recommends pinning actions to full length commit.

Keeping your actions up to date with Dependabot

With Dependabot version updates, when Dependabot identifies an outdated dependency, it raises a pull request to update the manifest to the latest version of the dependency. This is recommended by GitHub as well as The Open Source Security Foundation (OpenSSF).

Detect Vulnerabilities with SAST Workflow

Static Code Analysis (also known as Source Code Analysis) is usually performed as part of a Code Review (also known as clear-box testing) and is carried out at the Implementation phase of a Security Development Lifecycle (SDL). Static Code Analysis commonly refers to the running of Static Code Analysis tools that attempt to highlight possible vulnerabilities within ‘static’ (non-running) source code by using techniques such as Taint Analysis and Data Flow Analysis.

Feedback

For bug reports, feature requests, and general feedback; please email support@stepsecurity.io. To create such PRs, please visit https://app.stepsecurity.io/securerepo.

Signed-off-by: StepSecurity Bot bot@stepsecurity.io

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
@UlisesGascon UlisesGascon self-assigned this May 18, 2025
@github-advanced-security

Copy link
Copy Markdown

@UlisesGascon UlisesGascon merged commit a2b3285 into jshttp:master Jun 2, 2025
@UlisesGascon UlisesGascon mentioned this pull request Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants