Skip to content
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

ci: add main ci jobs #13

Merged
merged 9 commits into from
Feb 1, 2024
Merged

ci: add main ci jobs #13

merged 9 commits into from
Feb 1, 2024

Conversation

xopham
Copy link
Contributor

@xopham xopham commented Feb 1, 2024

No description provided.

@xopham xopham force-pushed the ci/add-main-ci branch 3 times, most recently from a64227c to ca268b3 Compare February 1, 2024 13:07
@github-advanced-security
Copy link

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.

.github/workflows/.reusable-docs.yaml Fixed Show fixed Hide fixed
@@ -0,0 +1,99 @@
name: build

Check failure

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
@@ -0,0 +1,177 @@
name: ci

Check failure

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
@@ -0,0 +1,84 @@
name: compliance

Check failure

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
.github/workflows/.reusable-docs.yaml Fixed Show fixed Hide fixed
@@ -0,0 +1,227 @@
name: sast

Check failure

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
@@ -0,0 +1,100 @@
name: sca

Check failure

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
@@ -0,0 +1,32 @@
name: unit-test

Check failure

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
@@ -0,0 +1,29 @@
name: pr

Check failure

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
@@ -0,0 +1,29 @@
name: push

Check failure

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
Copy link

github-actions bot commented Feb 1, 2024

Dependency Review

The following issues were found:
  • ✅ 0 vulnerable package(s)
  • ✅ 0 package(s) with incompatible licenses
  • ✅ 0 package(s) with invalid SPDX license definitions
  • ⚠️ 3 package(s) with unknown licenses.
See the Details below.

License Issues

tests/requirements.txt

PackageVersionLicenseIssue Type
requests-mock~> 1.11.0NullUnknown License

.github/workflows/.reusable-cleanup-registry.yml

PackageVersionLicenseIssue Type
snok/container-retention-policy3d27e6a0361deed0b7dc5099a82eadd07924b177NullUnknown License

.github/workflows/.reusable-sast.yml

PackageVersionLicenseIssue Type
bridgecrewio/checkov-action558f721c4bd65a6fc59b02448ffc792eb721cb9bNullUnknown License

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.yml
docs/requirements.txt
  • mike@~> 2.0.0
  • mkdocs-material@~> 9.4.14
tests/requirements.txt
  • aioresponses@~> 0.7.6
  • bandit@~> 1.7.7
  • bandit-sarif-formatter@~> 1.1.1
  • black@~> 24.1.1
  • freezegun@~> 1.2.2
  • parsedatetime@~> 2.6
  • pylint@~> 3.0.2
  • pytest-asyncio@~> 0.21.1
  • pytest-cov@~> 4.1.0
  • pytest-mock@~> 3.12.0
  • pytest-subprocess@~> 1.5.0
  • requests-mock@~> 1.11.0
  • setuptools@~> 69.0.2
  • wheel@~> 0.42.0

uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Install
run: |
pip3 install -r tests/requirements.txt

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Install Packages
run: pip3 install -r tests/requirements.txt
- name: Run Bandit

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
uses: actions/checkout@b4ffde65f46336ab88eb53be808477a3936bae11 # v4.1.1
- name: Install packages
run: pip3 install -r tests/requirements.txt
- name: Test formatting

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
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

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
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

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
Comment on lines +3 to +4
#permissions: {} #TODO: reactivate for non-private

Check failure

Code scanning / checkov

Ensure top-level permissions are not set to write-all Error

Ensure top-level permissions are not set to write-all
Comment on lines +3 to +4
#permissions: {} #TODO: reactivate for non-private

Check failure

Code scanning / checkov

Ensure top-level permissions are not set to write-all Error

Ensure top-level permissions are not set to write-all
@xopham xopham force-pushed the ci/add-main-ci branch 2 times, most recently from b2901b8 to ee2c2ee Compare February 1, 2024 14:26
.github/workflows/.reusable-docs.yml Fixed Show fixed Hide fixed
@@ -0,0 +1,43 @@
name: docs

Check failure

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
runs-on: ubuntu-latest
if: inputs.skip != 'all'
permissions:
contents: write

Check failure

Code scanning / Scorecard

Token-Permissions High

score is 0: jobLevel 'contents' permission set to 'write'
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

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
Comment on lines +3 to +4
#permissions: {} #TODO: reactivate for non-private

Check failure

Code scanning / checkov

Ensure top-level permissions are not set to write-all Error

Ensure top-level permissions are not set to write-all
git config user.email "connaisseur@securesystems.dev"
- name: Install
run: |
pip install -r docs/requirements.txt

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 8: pipCommand not pinned by hash
Click Remediation section below to solve this issue
@xopham xopham merged commit 1c7562d into dev Feb 1, 2024
25 of 29 checks passed
@xopham xopham deleted the ci/add-main-ci branch February 1, 2024 15:53
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.

1 participant