-
Notifications
You must be signed in to change notification settings - Fork 0
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
v0.1.0 release #14
v0.1.0 release #14
Conversation
xopham
commented
Feb 1, 2024
- ci: fix dependencies
- fix: ssl certificate overwrite error
- ci: add dependabot
- ci: add main ci jobs
- ci: compliance checks
- ci: sast
- docs: charts details
- ci: sca
- ci: docs
- ci: integration tests
- ci: workflow configurations
- ci: minor fixes
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Dependency ReviewThe following issues were found:
License Issuestests/requirements.txt
.github/workflows/.reusable-cleanup-registry.yml
.github/workflows/.reusable-sast.yml
requirements.txt
Scanned Manifest Files.github/workflows/.reusable-build.yml.github/workflows/.reusable-cleanup-registry.yml.github/workflows/.reusable-compliance.yml.github/workflows/.reusable-docs.yml.github/workflows/.reusable-sast.yml.github/workflows/.reusable-sca.yml.github/workflows/.reusable-unit-test.ymldocs/requirements.txt
requirements.txt
tests/requirements.txt
|
@@ -0,0 +1,99 @@ | |||
name: build |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
@@ -0,0 +1,177 @@ | |||
name: ci |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
@@ -0,0 +1,87 @@ | |||
name: compliance |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
@@ -0,0 +1,41 @@ | |||
name: integration-test |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
@@ -0,0 +1,235 @@ | |||
name: sast |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1 | ||
- name: Install | ||
run: | | ||
pip3 install -r tests/requirements.txt && pip3 install . |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
Click Remediation section below to solve this issue
@@ -0,0 +1,43 @@ | |||
name: docs |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
runs-on: ubuntu-latest | ||
if: inputs.skip != 'all' | ||
permissions: | ||
contents: write |
Check failure
Code scanning / Scorecard
Token-Permissions High
Remediation tip: Verify which permissions are needed and consider whether you can reduce them.
Click Remediation section below for further remediation help
@@ -0,0 +1,28 @@ | |||
name: tag |
Check failure
Code scanning / Scorecard
Token-Permissions High
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
git config user.email "connaisseur@securesystems.dev" | ||
- name: Install | ||
run: | | ||
pip install -r docs/requirements.txt |
Check warning
Code scanning / Scorecard
Pinned-Dependencies Medium
Click Remediation section below to solve this issue
#permissions: {} #TODO: reactivate for non-private | ||
|
Check failure
Code scanning / checkov
Ensure top-level permissions are not set to write-all Error
#permissions: {} #TODO: reactivate for non-private | ||
|
Check failure
Code scanning / checkov
Ensure top-level permissions are not set to write-all Error
#permissions: {} #TODO: reactivate for non-private | ||
|
Check failure
Code scanning / checkov
Ensure top-level permissions are not set to write-all Error