AI Slop Code Risk Monitor

MichaelCade/90DaysOfDevOps

SlopCodeMonitor badge for MichaelCade/90DaysOfDevOps Adjusted legacy signal; badge bands: 25 / 50 / 75 (different from dashboard bands).

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.

3.7 Low pattern signal View on GitHub

Open-Source Code Quality, Security and Technical Debt Review

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.

3.7
Adjusted Signal
3.7
Raw Pattern Score
100%
Time Factor
2026-06-24
Last Push
29.9K
Stars
Shell
Language
177.0K
Lines of Code
2.2K
Files
424
Pattern Hits
2026-10-31
Scan Date
0.01
HC Hit Rate

Risk Review · Payload v1

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.

Cognitive Ownership Risk 12.0/100 · LOW

Can maintainers explain intent, assumptions, and trade-offs? 355 finding(s).

Hallucinated Dependency & Supply Chain Risk 0.7/100 · LOW

Are imports declared and package/API names verified? 25 finding(s).

Agent Over-Engineering Ratio 4.9/100 · LOW

Are wrappers, guards, and repeated structures necessary? 45 finding(s).

PR Review Velocity Impact 16.9/100 · LOW

Which changes need focused human review? 424 finding(s).

What These Metrics Mean

Adjusted Signal
Legacy pattern score normalized per 1,000 scanned lines and multiplied by the repository-level time factor. It is not an estimate of AI authorship.
Raw Pattern Score
Sum of severity- and context-weighted pattern findings before applying the time factor.
Time Factor
A coarse multiplier based on repository last-push metadata. It does not identify when individual code was written.
Pattern Hits
Count of configured pattern findings. Review each location and surrounding code before acting.
HC Hit Rate
High- and critical-severity findings per scanned file. Severity is a configured detector weight, not proof of a vulnerability or authorship.
Lines / Files
Scan coverage denominators used by the legacy normalized score.

Pattern-Signal History

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.

Severity Breakdown

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.

CRITICAL 0HIGH 28MEDIUM 46LOW 350

Directory Score Breakdown

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.

Pattern Findings

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.

Over-Commented Block273 hits · 248 pts
SeverityFileLineSnippetContext
LOW…onfigmgmt/ansible-scenario6/roles/common/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…onfigmgmt/ansible-scenario6/roles/common/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml41COMMENT
LOW…onfigmgmt/ansible-scenario7/roles/common/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…onfigmgmt/ansible-scenario7/roles/common/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario7/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario7/roles/apache2/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario7/roles/nginx/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario7/roles/nginx/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario7/roles/mysql/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario7/roles/mysql/meta/main.yml41COMMENT
LOW…onfigmgmt/ansible-scenario5/roles/common/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…onfigmgmt/ansible-scenario5/roles/common/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario5/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario5/roles/apache2/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario5/roles/nginx/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario5/roles/nginx/meta/main.yml41COMMENT
LOW…onfigmgmt/ansible-scenario4/roles/common/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…onfigmgmt/ansible-scenario4/roles/common/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario4/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario4/roles/apache2/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario4/roles/nginx/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario4/roles/nginx/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario3/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario3/roles/apache2/meta/main.yml41COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml1# Default values for jenkins.COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml61 jenkinsWar: "/usr/share/jenkins/jenkins.war"COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml81 # initContainerEnv:COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml201 # agentListenerServiceType is the Kubernetes Service type for the JNLP agent service,COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml221 - 0.0.0.0/0COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml261 overwritePluginsFromImage: trueCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml281 additionalExistingSecrets: []COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml301COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml341 # If enabled: true, Jenkins Configuration as Code will be reloaded on-the-fly without a reboot. If false or not-sCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml361 # This TCP port will not be open in the pod (unless you specifically configure this), so Jenkins will not beCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml381 ## Note: To use it you should go to https://smee.io/new and update the url to the generete one.COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml421 # Override for the default paths that map requests to the backendCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml441 # Set this path to jenkinsUriPrefix above or use annotations to rewrite pathCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml461 apiVersion: "extensions/v1beta1"COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml501 # hostnames:COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml621 volumes: []COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml641 # defaultMode: "600"COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml661 # type: NfsCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml681 # Side container nameCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml701 # - key: "key"COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml721 # label: jenkins-pythonCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml741# # An example of overriding the jnlp containerCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml761 ## jenkins data Persistent Volume Storage ClassCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml821## Ref: https://github.com/maorfr/kube-tasksCOMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml841 activeDeadlineSeconds: ""COMMENT
LOW…onfigmgmt/ansible-scenario6/roles/common/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…onfigmgmt/ansible-scenario6/roles/common/meta/main.yml41COMMENT
LOW…nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…nfigmgmt/ansible-scenario6/roles/apache2/meta/main.yml41COMMENT
LOW…Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml21 # If this a Container Enabled role, provide the minimum Ansible Container version.COMMENT
LOW…Configmgmt/ansible-scenario6/roles/nginx/meta/main.yml41COMMENT
213 more matches not shown…
Cross-File Repetition23 hits · 115 pts
SeverityFileLineSnippetContext
HIGH2022/pl/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/vi/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/ja/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/zh_tw/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/zh_cn/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/ko/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/es/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: shell image: ubuntu command: - sleep args: - infinitySTRING
HIGH2022/pl/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/vi/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/ja/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/zh_tw/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/zh_cn/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/es/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/ko/Days/day73.md0apiversion: v1 kind: pod spec: containers: - name: maven image: maven command: - sleep args: - 99d - name: kaniko image:STRING
HIGH2022/pl/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/vi/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/ja/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/zh_tw/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/zh_cn/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
HIGH2022/es/Days/day73.md0/kaniko/executor --context `pwd` --destination michaelcade1/helloworld:latestSTRING
Structural Annotation Overuse36 hits · 81 pts
SeverityFileLineSnippetContext
LOW⚡2023/day53.md17### Step 1: Navigate to the AWS System Manager ConsoleCOMMENT
LOW⚡2023/day53.md24### Step 2: Choose a configuration typeCOMMENT
LOW⚡2023/day53.md30### Step 3: Specify configuration optionsCOMMENT
LOW⚡2023/day53.md39### Step 4: Deploy, Review, and Manage Your ResourcesCOMMENT
LOW⚡2023/day52.md24### Step 1: Create an AWS AccountCOMMENT
LOW⚡2023/day52.md28### Step 2: Set up IAMCOMMENT
LOW⚡2023/day52.md32### Step 3: Create an IAM UserCOMMENT
LOW⚡2023/day52.md36### Step 4: Create an IAM GroupCOMMENT
LOW⚡2023/day52.md40### Step 5: Assign Permissions to the IAM GroupCOMMENT
LOW⚡2023/day52.md44### Step 6: Test the IAM UserCOMMENT
LOW⚡2023/day55.md26### Step 1: Create an IAM roleCOMMENT
LOW⚡2023/day55.md30### Step 2: Create a CodePipeline pipelineCOMMENT
LOW⚡2023/day55.md34### Step 3: Test and deploy your code changesCOMMENT
LOW⚡2023/day50.md5## Step 1: Go to the AWS websiteCOMMENT
LOW⚡2023/day50.md10## Step 2: Create an AWS accountCOMMENT
LOW⚡2023/day50.md16## Step 3: Provide your account informationCOMMENT
LOW⚡2023/day50.md23## Step 4: Provide your payment informationCOMMENT
LOW⚡2023/day50.md29## Step 5: Select a support planCOMMENT
LOW⚡2023/ko/days/day53.md17### Step 1: AWS System Manager 콘솔로 이동COMMENT
LOW⚡2023/ko/days/day53.md24### Step 2: 구성 유형 선택COMMENT
LOW⚡2023/ko/days/day53.md30### Step 3: 구성 옵션 구체화COMMENT
LOW⚡2023/ko/days/day53.md39### Step 4: 리소스 배포, 검토 및 관리COMMENT
LOW⚡2023/ko/days/day52.md23### Step 1: AWS 계정 만들기COMMENT
LOW⚡2023/ko/days/day52.md27### Step 2: IAM 설정COMMENT
LOW⚡2023/ko/days/day52.md31### Step 3: IAM 사용자 생성COMMENT
LOW⚡2023/ko/days/day52.md35### Step 4: IAM 그룹 생성COMMENT
LOW⚡2023/ko/days/day52.md39### Step 5: IAM Group에 권한 할당COMMENT
LOW⚡2023/ko/days/day52.md43### Step 6: IAM 사용자 테스트COMMENT
LOW⚡2023/ko/days/day55.md26### Step 1: IAM 역할 만들기COMMENT
LOW⚡2023/ko/days/day55.md30### Step 2: CodePipeline 파이프라인 생성COMMENT
LOW⚡2023/ko/days/day55.md34### Step 3: 코드 변경 테스트 및 배포COMMENT
LOW⚡2023/ko/days/day50.md5## Step 1: AWS 웹사이트로 이동COMMENT
LOW⚡2023/ko/days/day50.md10## Step 2: AWS 계정 생성COMMENT
LOW⚡2023/ko/days/day50.md16## Step 3: 계정 정보 제공COMMENT
LOW⚡2023/ko/days/day50.md23## Step 4: 결제 정보 제공COMMENT
LOW⚡2023/ko/days/day50.md29## Step 5: 지원 계획 선택COMMENT
Self-Referential Comments20 hits · 60 pts
SeverityFileLineSnippetContext
MEDIUM2022/ja/Days/IaC/Hello-world/main.tf2 # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are settingCOMMENT
MEDIUM2022/ja/Days/Monitoring/EFK Stack/efk-stack.yaml8# Create a Headless services named elasticsearch, that will define a DNS domainCOMMENT
MEDIUM2022/ja/Days/Monitoring/EFK Stack/efk-stack.yaml11#Define the service in the namespaceCOMMENT
MEDIUM2022/ja/Days/Monitoring/Elastic Stack/setup/helpers.sh117# Create the given Elasticsearch user.COMMENT
MEDIUM2022/zh_tw/Days/IaC/Hello-world/main.tf2 # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are settingCOMMENT
MEDIUM2022/zh_tw/Days/Monitoring/EFK Stack/efk-stack.yaml8# Create a Headless services named elasticsearch, that will define a DNS domainCOMMENT
MEDIUM2022/zh_tw/Days/Monitoring/EFK Stack/efk-stack.yaml11#Define the service in the namespaceCOMMENT
MEDIUM…2/zh_tw/Days/Monitoring/Elastic Stack/setup/helpers.sh117# Create the given Elasticsearch user.COMMENT
MEDIUM2022/Days/IaC/Hello-world/main.tf2 # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are settingCOMMENT
MEDIUM2022/Days/Monitoring/EFK Stack/efk-stack.yaml8# Create a Headless services named elasticsearch, that will define a DNS domainCOMMENT
MEDIUM2022/Days/Monitoring/EFK Stack/efk-stack.yaml11#Define the service in the namespaceCOMMENT
MEDIUM2022/Days/Monitoring/Elastic Stack/setup/helpers.sh117# Create the given Elasticsearch user.COMMENT
MEDIUM2022/es/Days/IaC/Hello-world/main.tf2 # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are settingCOMMENT
MEDIUM2022/es/Days/Monitoring/EFK Stack/efk-stack.yaml8# Create a Headless services named elasticsearch, that will define a DNS domainCOMMENT
MEDIUM2022/es/Days/Monitoring/EFK Stack/efk-stack.yaml11#Define the service in the namespaceCOMMENT
MEDIUM2022/es/Days/Monitoring/Elastic Stack/setup/helpers.sh117# Create the given Elasticsearch user.COMMENT
MEDIUM2022/tr/Days/IaC/Hello-world/main.tf2 # This module is now only being tested with Terraform 0.13.x. However, to make upgrading easier, we are settingCOMMENT
MEDIUM2022/tr/Days/Monitoring/EFK Stack/efk-stack.yaml8# Create a Headless services named elasticsearch, that will define a DNS domainCOMMENT
MEDIUM2022/tr/Days/Monitoring/EFK Stack/efk-stack.yaml11#Define the service in the namespaceCOMMENT
MEDIUM2022/tr/Days/Monitoring/Elastic Stack/setup/helpers.sh117# Create the given Elasticsearch user.COMMENT
Decorative Section Separators20 hits · 60 pts
SeverityFileLineSnippetContext
MEDIUM…2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh9# --------------------------------------------------------COMMENT
MEDIUM…2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh23# --------------------------------------------------------COMMENT
MEDIUM…2/ja/Days/Monitoring/Elastic Stack/setup/entrypoint.sh31# --------------------------------------------------------COMMENT
MEDIUM…ensions/enterprise-search/config/enterprise-search.yml13## ----------------------------------------------------COMMENT
MEDIUM…h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh9# --------------------------------------------------------COMMENT
MEDIUM…h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh23# --------------------------------------------------------COMMENT
MEDIUM…h_tw/Days/Monitoring/Elastic Stack/setup/entrypoint.sh31# --------------------------------------------------------COMMENT
MEDIUM…ensions/enterprise-search/config/enterprise-search.yml13## ----------------------------------------------------COMMENT
MEDIUM2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh9# --------------------------------------------------------COMMENT
MEDIUM2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh23# --------------------------------------------------------COMMENT
MEDIUM2022/Days/Monitoring/Elastic Stack/setup/entrypoint.sh31# --------------------------------------------------------COMMENT
MEDIUM…ensions/enterprise-search/config/enterprise-search.yml13## ----------------------------------------------------COMMENT
MEDIUM…2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh9# --------------------------------------------------------COMMENT
MEDIUM…2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh23# --------------------------------------------------------COMMENT
MEDIUM…2/es/Days/Monitoring/Elastic Stack/setup/entrypoint.sh31# --------------------------------------------------------COMMENT
MEDIUM…ensions/enterprise-search/config/enterprise-search.yml13## ----------------------------------------------------COMMENT
MEDIUM…2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh9# --------------------------------------------------------COMMENT
MEDIUM…2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh23# --------------------------------------------------------COMMENT
MEDIUM…2/tr/Days/Monitoring/Elastic Stack/setup/entrypoint.sh31# --------------------------------------------------------COMMENT
MEDIUM…ensions/enterprise-search/config/enterprise-search.yml13## ----------------------------------------------------COMMENT
AI Response Leakage5 hits · 25 pts
SeverityFileLineSnippetContext
HIGH2022/pl/day40.md98I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could help guide the content CODE
HIGH2022/ja/Days/day40.md98I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the cCODE
HIGH2022/zh_tw/Days/day40.md98I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the cCODE
HIGH2022/zh_cn/Days/day40.md98I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could really help guide the cCODE
HIGH2022/Days/day40.md100I believe the next tab is quite new? But I thought for a project like #90DaysOfDevOps this could help guide the content CODE
Unused Imports25 hits · 25 pts
SeverityFileLineSnippetContext
LOW2022/ja/Days/Networking/backup.py1CODE
LOW2022/ja/Days/Networking/backup.py4CODE
LOW2022/ja/Days/Networking/backup.py5CODE
LOW2022/ja/Days/Networking/netmiko_con_multi.py3CODE
LOW2022/ja/Days/Networking/netmiko_con_multi_vlan.py3CODE
LOW2022/zh_tw/Days/Networking/backup.py1CODE
LOW2022/zh_tw/Days/Networking/backup.py4CODE
LOW2022/zh_tw/Days/Networking/backup.py5CODE
LOW2022/zh_tw/Days/Networking/netmiko_con_multi.py3CODE
LOW2022/zh_tw/Days/Networking/netmiko_con_multi_vlan.py3CODE
LOW2022/Days/Networking/backup.py1CODE
LOW2022/Days/Networking/backup.py4CODE
LOW2022/Days/Networking/backup.py5CODE
LOW2022/Days/Networking/netmiko_con_multi.py3CODE
LOW2022/Days/Networking/netmiko_con_multi_vlan.py3CODE
LOW2022/es/Days/Networking/backup.py1CODE
LOW2022/es/Days/Networking/backup.py4CODE
LOW2022/es/Days/Networking/backup.py5CODE
LOW2022/es/Days/Networking/netmiko_con_multi.py3CODE
LOW2022/es/Days/Networking/netmiko_con_multi_vlan.py3CODE
LOW2022/tr/Days/Networking/backup.py1CODE
LOW2022/tr/Days/Networking/backup.py4CODE
LOW2022/tr/Days/Networking/backup.py5CODE
LOW2022/tr/Days/Networking/netmiko_con_multi.py3CODE
LOW2022/tr/Days/Networking/netmiko_con_multi_vlan.py3CODE
Slop Phrases5 hits · 15 pts
SeverityFileLineSnippetContext
MEDIUM2022/ja/Days/CICD/Jenkins/jenkins-values.yml735# Here you can add additional agentsCOMMENT
MEDIUM2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml735# Here you can add additional agentsCOMMENT
MEDIUM2022/Days/CICD/Jenkins/jenkins-values.yml735# Here you can add additional agentsCOMMENT
MEDIUM2022/es/Days/CICD/Jenkins/jenkins-values.yml735# Here you can add additional agentsCOMMENT
MEDIUM2022/tr/Days/CICD/Jenkins/jenkins-values.yml735# Here you can add additional agentsCOMMENT
Redundant / Tautological Comments10 hits · 15 pts
SeverityFileLineSnippetContext
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml840 # Set this to terminate the job that is running/failing continously and set the job status to "Failed"COMMENT
LOW2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml840 # Set this to terminate the job that is running/failing continously and set the job status to "Failed"COMMENT
LOW2022/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/Days/CICD/Jenkins/jenkins-values.yml840 # Set this to terminate the job that is running/failing continously and set the job status to "Failed"COMMENT
LOW2022/es/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/es/Days/CICD/Jenkins/jenkins-values.yml840 # Set this to terminate the job that is running/failing continously and set the job status to "Failed"COMMENT
LOW2022/tr/Days/CICD/Jenkins/jenkins-values.yml101 # Set runAsUser to 1000 to let Jenkins run as non-root user 'jenkins' which exists in 'jenkins/jenkins' docker image.COMMENT
LOW2022/tr/Days/CICD/Jenkins/jenkins-values.yml840 # Set this to terminate the job that is running/failing continously and set the job status to "Failed"COMMENT
AI Slop Vocabulary5 hits · 8 pts
SeverityFileLineSnippetContext
LOW2022/ja/Days/CICD/Jenkins/jenkins-values.yml520 # The `groups` root object is added by default, simply add the rule entriesCOMMENT
LOW2022/zh_tw/Days/CICD/Jenkins/jenkins-values.yml520 # The `groups` root object is added by default, simply add the rule entriesCOMMENT
LOW2022/Days/CICD/Jenkins/jenkins-values.yml520 # The `groups` root object is added by default, simply add the rule entriesCOMMENT
LOW2022/es/Days/CICD/Jenkins/jenkins-values.yml520 # The `groups` root object is added by default, simply add the rule entriesCOMMENT
LOW2022/tr/Days/CICD/Jenkins/jenkins-values.yml520 # The `groups` root object is added by default, simply add the rule entriesCOMMENT
Excessive Try-Catch Wrapping1 hit · 2 pts
SeverityFileLineSnippetContext
MEDIUM2023/day43.md109 print("Something went wrong when writing to the file")CODE
Hyper-Verbose Identifiers1 hit · 1 pts
SeverityFileLineSnippetContext
LOW2024/day16.md343 async def get_author_and_book_via_search(self) -> PlaywrightResult:CODE