You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pyaedt is a critical dependency for our project (really appreciate all your works!), however, we are concerned about the risk of bad changes making into the repository, introducing vulnerabilities into our project given how prevalent software supply chain attacks have become.
token permission - no topLevel permission defined: .github/workflows/ci_cd.yml:1; no topLevel permission defined: .github/workflows/label.yml:1; no topLevel permission defined: .github/workflows/manual_draft.yml:1; no topLevel permission defined: .github/workflows/nightly-docs.yml:1; no topLevel permission defined: .github/workflows/unit_test_prerelease.yml:1. See https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions for more details.
Those seem to be concerns that can be addressed fairly quickly, and can help increase the trust of the package so much. Really appreciate it if the settings can be strengthened soon.
Run security scan against the pyaedt repo:
scorecard --repo=https://github.com/ansys/pyaedt --checks=Dangerous-Workflow,Maintained,Vulnerabilities,Binary-Artifacts,Branch-Protection,Code-Review,Token-Permissions,Signed-Releases,Dependency-Update-Tool --show-details
Which Operating System are you using?
Linux
Which Python version are you using?
3.11
Installed packages
pyaedt==0.8.11
The text was updated successfully, but these errors were encountered:
Before submitting the issue
Description of the bug
Repository security settings can be strengthened.
Pyaedt is a critical dependency for our project (really appreciate all your works!), however, we are concerned about the risk of bad changes making into the repository, introducing vulnerabilities into our project given how prevalent software supply chain attacks have become.
We used the tool https://github.com/ossf/scorecard?tab=readme-ov-file#using-scorecard to help us assess the risk of using pyaedt. It suggested that some areas seem to be weak against bad behaviors:
branch protection - no branch protection enabled for release/0.8; required approving review count is 1 on branch 'main'; code owners review is not required on branch 'main'. See https://github.com/ossf/scorecard/blob/main/docs/checks.md#branch-protection for more details.
token permission - no topLevel permission defined: .github/workflows/ci_cd.yml:1; no topLevel permission defined: .github/workflows/label.yml:1; no topLevel permission defined: .github/workflows/manual_draft.yml:1; no topLevel permission defined: .github/workflows/nightly-docs.yml:1; no topLevel permission defined: .github/workflows/unit_test_prerelease.yml:1. See https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions for more details.
signed-releases - The release artifacts are not signed, see https://github.com/ossf/scorecard/blob/main/docs/checks.md#signed-releases.
Those seem to be concerns that can be addressed fairly quickly, and can help increase the trust of the package so much. Really appreciate it if the settings can be strengthened soon.
Steps To Reproduce
See https://github.com/ossf/scorecard/tree/main?tab=readme-ov-file#scorecard-command-line-interface for instruction on running the tool.
Run security scan against the pyaedt repo:
scorecard --repo=https://github.com/ansys/pyaedt --checks=Dangerous-Workflow,Maintained,Vulnerabilities,Binary-Artifacts,Branch-Protection,Code-Review,Token-Permissions,Signed-Releases,Dependency-Update-Tool --show-details
Which Operating System are you using?
Linux
Which Python version are you using?
3.11
Installed packages
pyaedt==0.8.11
The text was updated successfully, but these errors were encountered: