Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

chore: apply security best practices#15097

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Conversation

step-security-bot
Copy link

Summary

This pull request is created byStepSecurity at the request of@matifali. Please merge the Pull Request to incorporate the requested changes. Please tag@matifali 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.

Harden Runner

Harden-Runner is an open-source security agent for the GitHub-hosted runner to prevent software supply chain attacks. It prevents exfiltration of credentials, detects tampering of source code during build, and enables running jobs withoutsudo access.

Harden runner usage

You can find link to view insights and policy recommendation in the build log

Please refer todocumentation to find more details.

Add Dependency Review Workflow

The Dependency Review Workflow enforces dependency reviews on your pull requests. The action scans for vulnerable versions of dependencies introduced by package version changes in pull requests, and warns you about the associated security vulnerabilities. This gives you better visibility of what's changing in a pull request, and helps prevent vulnerabilities being added to your repository.

Feedback

For bug reports, feature requests, and general feedback; please emailsupport@stepsecurity.io. To create such PRs, please visithttps://app.stepsecurity.io/securerepo.

Signed-off-by: StepSecurity Botbot@stepsecurity.io

Signed-off-by: StepSecurity Bot <bot@stepsecurity.io>
@cdr-botcdr-botbot added the communityPull Requests and issues created by the community. labelOct 15, 2024
@github-actionsGitHub Actions
Copy link

github-actionsbot commentedOct 15, 2024
edited
Loading


Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you all sign ourContributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.


I have read the CLA Document and I hereby sign the CLA


1 out of2 committers have signed the CLA.
✅ (matifali)[https://github.com/matifali]
@step-security-bot
You can retrigger this bot by commentingrecheck in this Pull Request.Posted by theCLA Assistant Lite bot.

@matifalimatifali changed the title[StepSecurity] Apply security best practiceschore: apply security best practicesOct 15, 2024
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsOct 15, 2024
@matifalimatifali reopened thisOct 15, 2024
@github-actionsgithub-actionsbot deleted the stepsecurity_remediation_1729029758 branchApril 16, 2025 06:52
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.
Reviewers
No reviews
Labels
communityPull Requests and issues created by the community.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

2 participants
@step-security-bot@matifali

[8]ページ先頭

©2009-2025 Movatter.jp