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
docs: deliver daily Omni-Sentinel operational report and harden CI/CD
- Generate live G-SRI and attestation telemetry report.
- Pin all GitHub Actions to commit SHAs for security compliance.
- Fix DeepSource analyzer config and Netlify rule formatting.
- Refactor server.js for CodeQL security and Deno linting compliance.
- Add missing process/buffer imports in Next.js and backend.
Co-authored-by: OneFineStarstuff <87420139+OneFineStarstuff@users.noreply.github.com>
# required to fetch internal or private CodeQL packs
35
+
# required to fetch internal or private CodeQL packs
36
36
packages: read
37
37
38
-
# only required for workflows in private repositories
38
+
# only required for workflows in private repositories
39
39
actions: read
40
40
contents: read
41
41
@@ -45,37 +45,37 @@ jobs:
45
45
include:
46
46
- language: python
47
47
build-mode: none
48
-
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
49
-
# Use `c-cpp` to analyze code written in C, C++ or both
50
-
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
51
-
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
52
-
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
53
-
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
54
-
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
55
-
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
48
+
# CodeQL supports the following values keywords for 'language': 'c-cpp', 'csharp', 'go', 'java-kotlin', 'javascript-typescript', 'python', 'ruby', 'swift'
49
+
# Use `c-cpp` to analyze code written in C, C++ or both
50
+
# Use 'java-kotlin' to analyze code written in Java, Kotlin or both
51
+
# Use 'javascript-typescript' to analyze code written in JavaScript, TypeScript or both
52
+
# To learn more about changing the languages that are analyzed or customizing the build mode for your analysis,
53
+
# see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/customizing-your-advanced-setup-for-code-scanning.
54
+
# If you are analyzing a compiled language, you can modify the 'build-mode' for that language to customize how
55
+
# your codebase is analyzed, see https://docs.github.com/en/code-security/code-scanning/creating-an-advanced-setup-for-code-scanning/codeql-code-scanning-for-compiled-languages
# If you wish to specify custom queries, you can do so here or in a config file.
67
-
# By default, queries listed here will override any specified in a config file.
68
-
# Prefix the list here with "+" to use these queries and those in the config file.
66
+
# If you wish to specify custom queries, you can do so here or in a config file.
67
+
# By default, queries listed here will override any specified in a config file.
68
+
# Prefix the list here with "+" to use these queries and those in the config file.
69
69
70
-
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
71
-
# queries: security-extended,security-and-quality
70
+
# For more details on CodeQL's query packs, refer to: https://docs.github.com/en/code-security/code-scanning/automatically-scanning-your-code-for-vulnerabilities-and-errors/configuring-code-scanning#using-queries-in-ql-packs
71
+
# queries: security-extended,security-and-quality
72
72
73
-
# If the analyze step fails for one of the languages you are analyzing with
74
-
# "We were unable to automatically build your code", modify the matrix above
75
-
# to set the build mode to "manual" for that language. Then modify this step
76
-
# to build your code.
77
-
# ℹ️ Command-line programs to run using the OS shell.
78
-
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
73
+
# If the analyze step fails for one of the languages you are analyzing with
74
+
# "We were unable to automatically build your code", modify the matrix above
75
+
# to set the build mode to "manual" for that language. Then modify this step
76
+
# to build your code.
77
+
# ℹ️ Command-line programs to run using the OS shell.
78
+
# 📚 See https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#jobsjob_idstepsrun
0 commit comments