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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Introduce workflows for receiving comments on a PR #1357

Draft

rickie wants to merge 5 commits into master from rossendrijver/setup_comments_for_ep

Draft

Introduce workflows for receiving comments on a PR #1357

Update command

GitHub Advanced Security / Scorecard failed Oct 14, 2024 in 3s

1 configuration not found

Warning: Code scanning may not have found all the alerts introduced by this pull request, because 1 configuration present on refs/heads/master was not found:

Actions workflow (`openssf-scorecard.yml`)

❓ supply-chain/branch-protection

New alerts in code changed by this pull request

Security Alerts:

2 high
8 medium

See annotations below for details.

View all branch alerts.

Annotations

Check failure on line 1 in .github/workflows/comment-pr.yml

Code scanning / Scorecard

Token-Permissions High

score is 0: no topLevel permission defined
Remediation tip: Visit https://app.stepsecurity.io/secureworkflow.
Tick the 'Restrict permissions for GITHUB_TOKEN'
Untick other options
NOTE: If you want to resolve multiple issues at once, you can visit https://app.stepsecurity.io/securerepo instead.
Click Remediation section below for further remediation help

Check warning on line 23 in .github/workflows/comment-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 29 in .github/workflows/comment-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 40 in .github/workflows/comment-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 52 in .github/workflows/comment-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: third-party GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 40 in .github/workflows/pitest-update-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: third-party GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check failure on line 1 in .github/workflows/receive-pr.yml

Code scanning / Scorecard

Token-Permissions High

score is 0: no topLevel permission defined
Remediation tip: Visit https://app.stepsecurity.io/secureworkflow.
Tick the 'Restrict permissions for GITHUB_TOKEN'
Untick other options
NOTE: If you want to resolve multiple issues at once, you can visit https://app.stepsecurity.io/securerepo instead.
Click Remediation section below for further remediation help

Check warning on line 22 in .github/workflows/receive-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 37 in .github/workflows/receive-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue

Check warning on line 52 in .github/workflows/receive-pr.yml

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: GitHub-owned GitHubAction not pinned by hash
Click Remediation section below to solve this issue