This repository started out as a learning in public project for myself and has now become a structured learning map for many in the community. We have 3 years under our belt covering all things DevOps, including Principles, Processes, Tooling and Use Cases surrounding this vast topic.
This report summarizes scanner evidence for MichaelCade/90DaysOfDevOps, a Shell project with 29,917 GitHub stars. SynthScan examined 177,007 lines of code across 2166 source files, recording 424 pattern matches distributed across 12 syntactic categories. The legacy adjusted pattern signal is 3.7 (Low pattern signal); it is not an authorship estimate.
Use the findings to ask whether maintainers can explain intent, verify dependencies, simplify unnecessary scaffolding, and focus review effort. Risk Payload v1 adds ownership, supply-chain, over-engineering, and review-effort vectors when available. These are prompts for human verification, not probabilities, security findings, or measured maintenance costs.
Use each vector to guide manual verification of the underlying findings.
Payload schema: 1.0.0 · Engine: 2.0.0 · Scoring: heuristic-density-v1 · Scan date: 2026-10-31.
Can maintainers explain intent, assumptions, and trade-offs? 355 finding(s).
Are imports declared and package/API names verified? 25 finding(s).
Are wrappers, guards, and repeated structures necessary? 45 finding(s).
Which changes need focused human review? 424 finding(s).
This chart tracks the legacy adjusted pattern score across scan runs. Changes can reflect source changes, scan coverage, or detector/scoring versions; they do not measure AI adoption or prove that a team refactored code. Compare runs only when their scoring versions are compatible. The dashed line tracks the raw pattern-hit count.
Groups findings by configured severity weight. Severity is not a confidence estimate, security rating, or proof that a package is missing. Verify imports against the project's manifests and inspect each finding in its local design context.
This horizontal bar chart shows where configured pattern scores accumulate across directories. Treat the bars as locations to inspect, not as evidence of authorship or code quality. Use the file-level findings to decide whether a directory needs a focused ownership, dependency, complexity, or review check.
The scanner identified 424 distinct pattern matches across 12 syntactic categories. Each entry below represents a discrete location in the source code where the engine recorded a detector match to inspect in context. Expand any category row to inspect the individual file paths, line numbers, code snippets, and the lexical context (CODE, COMMENT, or STRING) in which each match was detected.
Reading the findings table: The Severity column indicates the configured finding weight (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — legacy comment-context matches receive a ×1.5 score weight. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier under the legacy scoring model.
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | …onfigmgmt/ansible-scenario6/roles/common/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …onfigmgmt/ansible-scenario6/roles/common/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml | 41 | COMMENT | |
| LOW | …onfigmgmt/ansible-scenario7/roles/common/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …onfigmgmt/ansible-scenario7/roles/common/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario7/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario7/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario7/roles/nginx/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario7/roles/nginx/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario7/roles/mysql/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario7/roles/mysql/meta/main.yml | 41 | COMMENT | |
| LOW | …onfigmgmt/ansible-scenario5/roles/common/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …onfigmgmt/ansible-scenario5/roles/common/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario5/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario5/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario5/roles/nginx/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario5/roles/nginx/meta/main.yml | 41 | COMMENT | |
| LOW | …onfigmgmt/ansible-scenario4/roles/common/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …onfigmgmt/ansible-scenario4/roles/common/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario4/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario4/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario4/roles/nginx/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario4/roles/nginx/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario3/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario3/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 1 | # Default values for jenkins. | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 61 | jenkinsWar: "/usr/share/jenkins/jenkins.war" | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 81 | # initContainerEnv: | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 201 | # agentListenerServiceType is the Kubernetes Service type for the JNLP agent service, | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 221 | - 0.0.0.0/0 | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 261 | overwritePluginsFromImage: true | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 281 | additionalExistingSecrets: [] | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 301 | COMMENT | |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 341 | # If enabled: true, Jenkins Configuration as Code will be reloaded on-the-fly without a reboot. If false or not-s | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 361 | # This TCP port will not be open in the pod (unless you specifically configure this), so Jenkins will not be | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 381 | ## Note: To use it you should go to https://smee.io/new and update the url to the generete one. | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 421 | # Override for the default paths that map requests to the backend | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 441 | # Set this path to jenkinsUriPrefix above or use annotations to rewrite path | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 461 | apiVersion: "extensions/v1beta1" | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 501 | # hostnames: | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 621 | volumes: [] | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 641 | # defaultMode: "600" | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 661 | # type: Nfs | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 681 | # Side container name | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 701 | # - key: "key" | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 721 | # label: jenkins-python | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 741 | # # An example of overriding the jnlp container | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 761 | ## jenkins data Persistent Volume Storage Class | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 821 | ## Ref: https://github.com/maorfr/kube-tasks | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 841 | activeDeadlineSeconds: "" | COMMENT |
| LOW | …onfigmgmt/ansible-scenario6/roles/common/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …onfigmgmt/ansible-scenario6/roles/common/meta/main.yml | 41 | COMMENT | |
| LOW | …nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml | 41 | COMMENT | |
| LOW | …Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml | 21 | # If this a Container Enabled role, provide the minimum Ansible Container version. | COMMENT |
| LOW | …Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml | 41 | COMMENT | |
| 213 more matches not shown… | ||||
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | 2022/pl/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/vi/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/ja/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/zh_tw/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/zh_cn/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/ko/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/es/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinity | STRING |
| HIGH | 2022/pl/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/vi/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/ja/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/zh_tw/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/zh_cn/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/es/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/ko/Days/day73.md | 0 | apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image: | STRING |
| HIGH | 2022/pl/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/vi/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/ja/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/zh_tw/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/zh_cn/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| HIGH | 2022/es/Days/day73.md | 0 | /kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latest | STRING |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW⚡ | 2023/day53.md | 17 | ### Step 1: Navigate to the AWS System Manager Console | COMMENT |
| LOW⚡ | 2023/day53.md | 24 | ### Step 2: Choose a configuration type | COMMENT |
| LOW⚡ | 2023/day53.md | 30 | ### Step 3: Specify configuration options | COMMENT |
| LOW⚡ | 2023/day53.md | 39 | ### Step 4: Deploy, Review, and Manage Your Resources | COMMENT |
| LOW⚡ | 2023/day52.md | 24 | ### Step 1: Create an AWS Account | COMMENT |
| LOW⚡ | 2023/day52.md | 28 | ### Step 2: Set up IAM | COMMENT |
| LOW⚡ | 2023/day52.md | 32 | ### Step 3: Create an IAM User | COMMENT |
| LOW⚡ | 2023/day52.md | 36 | ### Step 4: Create an IAM Group | COMMENT |
| LOW⚡ | 2023/day52.md | 40 | ### Step 5: Assign Permissions to the IAM Group | COMMENT |
| LOW⚡ | 2023/day52.md | 44 | ### Step 6: Test the IAM User | COMMENT |
| LOW⚡ | 2023/day55.md | 26 | ### Step 1: Create an IAM role | COMMENT |
| LOW⚡ | 2023/day55.md | 30 | ### Step 2: Create a CodePipeline pipeline | COMMENT |
| LOW⚡ | 2023/day55.md | 34 | ### Step 3: Test and deploy your code changes | COMMENT |
| LOW⚡ | 2023/day50.md | 5 | ## Step 1: Go to the AWS website | COMMENT |
| LOW⚡ | 2023/day50.md | 10 | ## Step 2: Create an AWS account | COMMENT |
| LOW⚡ | 2023/day50.md | 16 | ## Step 3: Provide your account information | COMMENT |
| LOW⚡ | 2023/day50.md | 23 | ## Step 4: Provide your payment information | COMMENT |
| LOW⚡ | 2023/day50.md | 29 | ## Step 5: Select a support plan | COMMENT |
| LOW⚡ | 2023/ko/days/day53.md | 17 | ### Step 1: AWS System Manager 콘솔로 이동 | COMMENT |
| LOW⚡ | 2023/ko/days/day53.md | 24 | ### Step 2: 구성 유형 선택 | COMMENT |
| LOW⚡ | 2023/ko/days/day53.md | 30 | ### Step 3: 구성 옵션 구체화 | COMMENT |
| LOW⚡ | 2023/ko/days/day53.md | 39 | ### Step 4: 리소스 배포, 검토 및 관리 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 23 | ### Step 1: AWS 계정 만들기 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 27 | ### Step 2: IAM 설정 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 31 | ### Step 3: IAM 사용자 생성 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 35 | ### Step 4: IAM 그룹 생성 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 39 | ### Step 5: IAM Group에 권한 할당 | COMMENT |
| LOW⚡ | 2023/ko/days/day52.md | 43 | ### Step 6: IAM 사용자 테스트 | COMMENT |
| LOW⚡ | 2023/ko/days/day55.md | 26 | ### Step 1: IAM 역할 만들기 | COMMENT |
| LOW⚡ | 2023/ko/days/day55.md | 30 | ### Step 2: CodePipeline 파이프라인 생성 | COMMENT |
| LOW⚡ | 2023/ko/days/day55.md | 34 | ### Step 3: 코드 변경 테스트 및 배포 | COMMENT |
| LOW⚡ | 2023/ko/days/day50.md | 5 | ## Step 1: AWS 웹사이트로 이동 | COMMENT |
| LOW⚡ | 2023/ko/days/day50.md | 10 | ## Step 2: AWS 계정 생성 | COMMENT |
| LOW⚡ | 2023/ko/days/day50.md | 16 | ## Step 3: 계정 정보 제공 | COMMENT |
| LOW⚡ | 2023/ko/days/day50.md | 23 | ## Step 4: 결제 정보 제공 | COMMENT |
| LOW⚡ | 2023/ko/days/day50.md | 29 | ## Step 5: 지원 계획 선택 | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | 2022/ja/Days/IaC/Hello-world/main.tf | 2 | # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are setting | COMMENT |
| MEDIUM | 2022/ja/Days/Monitoring/EFK Stack/efk-stack.yaml | 8 | # Create a Headless services named elasticsearch, that will define a DNS domain | COMMENT |
| MEDIUM | 2022/ja/Days/Monitoring/EFK Stack/efk-stack.yaml | 11 | #Define the service in the namespace | COMMENT |
| MEDIUM | 2022/ja/Days/Monitoring/Elastic Stack/setup/helpers.sh | 117 | # Create the given Elasticsearch user. | COMMENT |
| MEDIUM | 2022/zh_tw/Days/IaC/Hello-world/main.tf | 2 | # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are setting | COMMENT |
| MEDIUM | 2022/zh_tw/Days/Monitoring/EFK Stack/efk-stack.yaml | 8 | # Create a Headless services named elasticsearch, that will define a DNS domain | COMMENT |
| MEDIUM | 2022/zh_tw/Days/Monitoring/EFK Stack/efk-stack.yaml | 11 | #Define the service in the namespace | COMMENT |
| MEDIUM | …2/zh_tw/Days/Monitoring/Elastic Stack/setup/helpers.sh | 117 | # Create the given Elasticsearch user. | COMMENT |
| MEDIUM | 2022/Days/IaC/Hello-world/main.tf | 2 | # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are setting | COMMENT |
| MEDIUM | 2022/Days/Monitoring/EFK Stack/efk-stack.yaml | 8 | # Create a Headless services named elasticsearch, that will define a DNS domain | COMMENT |
| MEDIUM | 2022/Days/Monitoring/EFK Stack/efk-stack.yaml | 11 | #Define the service in the namespace | COMMENT |
| MEDIUM | 2022/Days/Monitoring/Elastic Stack/setup/helpers.sh | 117 | # Create the given Elasticsearch user. | COMMENT |
| MEDIUM | 2022/es/Days/IaC/Hello-world/main.tf | 2 | # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are setting | COMMENT |
| MEDIUM | 2022/es/Days/Monitoring/EFK Stack/efk-stack.yaml | 8 | # Create a Headless services named elasticsearch, that will define a DNS domain | COMMENT |
| MEDIUM | 2022/es/Days/Monitoring/EFK Stack/efk-stack.yaml | 11 | #Define the service in the namespace | COMMENT |
| MEDIUM | 2022/es/Days/Monitoring/Elastic Stack/setup/helpers.sh | 117 | # Create the given Elasticsearch user. | COMMENT |
| MEDIUM | 2022/tr/Days/IaC/Hello-world/main.tf | 2 | # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are setting | COMMENT |
| MEDIUM | 2022/tr/Days/Monitoring/EFK Stack/efk-stack.yaml | 8 | # Create a Headless services named elasticsearch, that will define a DNS domain | COMMENT |
| MEDIUM | 2022/tr/Days/Monitoring/EFK Stack/efk-stack.yaml | 11 | #Define the service in the namespace | COMMENT |
| MEDIUM | 2022/tr/Days/Monitoring/Elastic Stack/setup/helpers.sh | 117 | # Create the given Elasticsearch user. | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | …2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 9 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 23 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 31 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …ensions/enterprise-search/config/enterprise-search.yml | 13 | ## ---------------------------------------------------- | COMMENT |
| MEDIUM | …h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 9 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 23 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 31 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …ensions/enterprise-search/config/enterprise-search.yml | 13 | ## ---------------------------------------------------- | COMMENT |
| MEDIUM | 2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 9 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | 2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 23 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | 2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 31 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …ensions/enterprise-search/config/enterprise-search.yml | 13 | ## ---------------------------------------------------- | COMMENT |
| MEDIUM | …2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 9 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 23 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 31 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …ensions/enterprise-search/config/enterprise-search.yml | 13 | ## ---------------------------------------------------- | COMMENT |
| MEDIUM | …2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 9 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 23 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh | 31 | # -------------------------------------------------------- | COMMENT |
| MEDIUM | …ensions/enterprise-search/config/enterprise-search.yml | 13 | ## ---------------------------------------------------- | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| HIGH | 2022/pl/day40.md | 98 | I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could help guide the content | CODE |
| HIGH | 2022/ja/Days/day40.md | 98 | I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the c | CODE |
| HIGH | 2022/zh_tw/Days/day40.md | 98 | I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the c | CODE |
| HIGH | 2022/zh_cn/Days/day40.md | 98 | I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the c | CODE |
| HIGH | 2022/Days/day40.md | 100 | I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could help guide the content | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | 2022/ja/Days/Networking/backup.py | 1 | CODE | |
| LOW | 2022/ja/Days/Networking/backup.py | 4 | CODE | |
| LOW | 2022/ja/Days/Networking/backup.py | 5 | CODE | |
| LOW | 2022/ja/Days/Networking/netmiko_con_multi.py | 3 | CODE | |
| LOW | 2022/ja/Days/Networking/netmiko_con_multi_vlan.py | 3 | CODE | |
| LOW | 2022/zh_tw/Days/Networking/backup.py | 1 | CODE | |
| LOW | 2022/zh_tw/Days/Networking/backup.py | 4 | CODE | |
| LOW | 2022/zh_tw/Days/Networking/backup.py | 5 | CODE | |
| LOW | 2022/zh_tw/Days/Networking/netmiko_con_multi.py | 3 | CODE | |
| LOW | 2022/zh_tw/Days/Networking/netmiko_con_multi_vlan.py | 3 | CODE | |
| LOW | 2022/Days/Networking/backup.py | 1 | CODE | |
| LOW | 2022/Days/Networking/backup.py | 4 | CODE | |
| LOW | 2022/Days/Networking/backup.py | 5 | CODE | |
| LOW | 2022/Days/Networking/netmiko_con_multi.py | 3 | CODE | |
| LOW | 2022/Days/Networking/netmiko_con_multi_vlan.py | 3 | CODE | |
| LOW | 2022/es/Days/Networking/backup.py | 1 | CODE | |
| LOW | 2022/es/Days/Networking/backup.py | 4 | CODE | |
| LOW | 2022/es/Days/Networking/backup.py | 5 | CODE | |
| LOW | 2022/es/Days/Networking/netmiko_con_multi.py | 3 | CODE | |
| LOW | 2022/es/Days/Networking/netmiko_con_multi_vlan.py | 3 | CODE | |
| LOW | 2022/tr/Days/Networking/backup.py | 1 | CODE | |
| LOW | 2022/tr/Days/Networking/backup.py | 4 | CODE | |
| LOW | 2022/tr/Days/Networking/backup.py | 5 | CODE | |
| LOW | 2022/tr/Days/Networking/netmiko_con_multi.py | 3 | CODE | |
| LOW | 2022/tr/Days/Networking/netmiko_con_multi_vlan.py | 3 | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 735 | # Here you can add additional agents | COMMENT |
| MEDIUM | 2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml | 735 | # Here you can add additional agents | COMMENT |
| MEDIUM | 2022/Days/CICD/Jenkins/jenkins-values.yml | 735 | # Here you can add additional agents | COMMENT |
| MEDIUM | 2022/es/Days/CICD/Jenkins/jenkins-values.yml | 735 | # Here you can add additional agents | COMMENT |
| MEDIUM | 2022/tr/Days/CICD/Jenkins/jenkins-values.yml | 735 | # Here you can add additional agents | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 840 | # Set this to terminate the job that is running/failing continously and set the job status to "Failed" | COMMENT |
| LOW | 2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml | 840 | # Set this to terminate the job that is running/failing continously and set the job status to "Failed" | COMMENT |
| LOW | 2022/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/Days/CICD/Jenkins/jenkins-values.yml | 840 | # Set this to terminate the job that is running/failing continously and set the job status to "Failed" | COMMENT |
| LOW | 2022/es/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/es/Days/CICD/Jenkins/jenkins-values.yml | 840 | # Set this to terminate the job that is running/failing continously and set the job status to "Failed" | COMMENT |
| LOW | 2022/tr/Days/CICD/Jenkins/jenkins-values.yml | 101 | # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image. | COMMENT |
| LOW | 2022/tr/Days/CICD/Jenkins/jenkins-values.yml | 840 | # Set this to terminate the job that is running/failing continously and set the job status to "Failed" | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | 2022/ja/Days/CICD/Jenkins/jenkins-values.yml | 520 | # The `groups` root object is added by default, simply add the rule entries | COMMENT |
| LOW | 2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml | 520 | # The `groups` root object is added by default, simply add the rule entries | COMMENT |
| LOW | 2022/Days/CICD/Jenkins/jenkins-values.yml | 520 | # The `groups` root object is added by default, simply add the rule entries | COMMENT |
| LOW | 2022/es/Days/CICD/Jenkins/jenkins-values.yml | 520 | # The `groups` root object is added by default, simply add the rule entries | COMMENT |
| LOW | 2022/tr/Days/CICD/Jenkins/jenkins-values.yml | 520 | # The `groups` root object is added by default, simply add the rule entries | COMMENT |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| MEDIUM | 2023/day43.md | 109 | print("Something went wrong when writing to the file") | CODE |
| Severity | File | Line | Snippet | Context |
|---|---|---|---|---|
| LOW | 2024/day16.md | 343 | async def get_author_and_book_via_search(self) -> PlaywrightResult: | CODE |