Repository Analysis

MichaelCade/90DaysOfDevOps

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 Likely human-written View on GitHub

Analysis Overview

This report presents the forensic synthetic code analysis of MichaelCade/90DaysOfDevOps, a Shell project with 29,596 GitHub stars. SynthScan v2.0 examined 177,007 lines of code across 2166 source files, recording 424 pattern matches distributed across 12 syntactic categories. The overall adjusted score of 3.7 places this repository in the Likely human-written band.

The scanner applied 160+ deterministic lexical heuristics, multi-line block detectors, abstract syntax tree depth profilers, and a cross-file Jaccard similarity matrix to construct a statistically normalised synthetic code estimate. All matches are individually weighted by severity coefficient and contextual multiplier before summation, and the resulting headline score is temporally discounted to account for the repository's development history relative to the commercial emergence of large language model coding tooling (November 2022 onward).

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

What These Metrics Mean

Adjusted Score
Primary synthetic code indicator. Raw score normalised per 1,000 lines of code and multiplied by the temporal discount factor. This is the definitive comparative metric — use it to rank repositories by AI authorship density.
Raw Score
The unmodified sum of all severity-weighted, context-multiplied pattern match scores before temporal discounting. Reflects the absolute signal strength independent of when the repository was last active.
Time Factor
The temporal discount multiplier (0–100%) applied to the raw score. Repositories last updated before ChatGPT's launch (Nov 2022) receive a 5% factor. Full signal is only assigned to repositories active in the post-adoption era (Jan 2024+).
Pattern Hits
Total count of individual pattern matches across all files and categories. A high hit count with a low score may indicate a very large codebase with isolated AI snippets; a low count with a high score indicates dense, concentrated AI signatures.
HC Hit Rate
High+Critical pattern hits per file, averaged across the repository. This orthogonal signal catches repositories where a few files are densely packed with high-severity AI tells — a strong indicator even when the normalised score appears moderate due to codebase size.
Lines of Code / Files
Total lines and files analysed. The scanner examines 94 file extensions. These denominators are used to normalise the score, enabling fair comparison between repositories of vastly different sizes.

Score History

This chart maps the temporal evolution of the adjusted synthetic code score across successive scan runs. An upward trajectory indicates ongoing incorporation of AI-generated code or expanding LLM-assisted scaffolding; a stable or declining trajectory may reflect active human refactoring, code removal, or the adoption of stricter authorship policies. The dashed secondary line (right axis) independently tracks total raw pattern hit count, which can diverge from the normalised score when codebase size changes significantly between scans.

Severity Breakdown

Classifies detected patterns by their diagnostic confidence and structural impact. CRITICAL patterns (coefficient 10) represent definitive synthetic signatures — hallucinated imports, explicit LLM attribution metadata — virtually never produced by human authors. HIGH (5) indicates strong structural tells such as cross-file repetition or cross-linguistic idioms. MEDIUM (2) covers recognisable conversational padding and AI-specific vocabulary. LOW (1) captures subtle indicators like tautological comments and generic boilerplate that require density to carry independent signal.

CRITICAL 0HIGH 28MEDIUM 46LOW 350

Directory Score Breakdown

This horizontal bar chart decomposes the repository's raw synthetic code score by top-level directory, allowing you to pinpoint precisely which modules or components carry the highest AI authorship density. Directories with disproportionately high scores relative to their size warrant targeted manual review: concentrated AI signatures often trace back to mass-generated configuration layers, auto-ported test suites, LLM-scaffolded boilerplate classes, or entire subsystems authored under heavy copilot assistance. Use this view to prioritise your human code-review effort.

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 statistically significant AI authorship indicator. 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 diagnostic confidence level (CRITICAL / HIGH / MEDIUM / LOW). The Context column identifies whether the match occurred inside executable code, an inline comment, or a string literal — comment-context matches receive a ×1.5 weight because LLMs systematically over-annotate. The ⚡ bolt icon marks clustered matches: three or more patterns within a 10-line window, each receiving an additional ×1.5 density multiplier as dense clusters constitute far stronger evidence of synthetic authorship than isolated hits.

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
LOW2023/day53.md17### Step 1: Navigate to the AWS System Manager ConsoleCOMMENT
LOW2023/day53.md24### Step 2: Choose a configuration typeCOMMENT
LOW2023/day53.md30### Step 3: Specify configuration optionsCOMMENT
LOW2023/day53.md39### Step 4: Deploy, Review, and Manage Your ResourcesCOMMENT
LOW2023/day52.md24### Step 1: Create an AWS AccountCOMMENT
LOW2023/day52.md28### Step 2: Set up IAMCOMMENT
LOW2023/day52.md32### Step 3: Create an IAM UserCOMMENT
LOW2023/day52.md36### Step 4: Create an IAM GroupCOMMENT
LOW2023/day52.md40### Step 5: Assign Permissions to the IAM GroupCOMMENT
LOW2023/day52.md44### Step 6: Test the IAM UserCOMMENT
LOW2023/day55.md26### Step 1: Create an IAM roleCOMMENT
LOW2023/day55.md30### Step 2: Create a CodePipeline pipelineCOMMENT
LOW2023/day55.md34### Step 3: Test and deploy your code changesCOMMENT
LOW2023/day50.md5## Step 1: Go to the AWS websiteCOMMENT
LOW2023/day50.md10## Step 2: Create an AWS accountCOMMENT
LOW2023/day50.md16## Step 3: Provide your account informationCOMMENT
LOW2023/day50.md23## Step 4: Provide your payment informationCOMMENT
LOW2023/day50.md29## Step 5: Select a support planCOMMENT
LOW2023/ko/days/day53.md17### Step 1: AWS System Manager 콘솔로 이동COMMENT
LOW2023/ko/days/day53.md24### Step 2: 구성 유형 선택COMMENT
LOW2023/ko/days/day53.md30### Step 3: 구성 옵션 구체화COMMENT
LOW2023/ko/days/day53.md39### Step 4: 리소스 배포, 검토 및 관리COMMENT
LOW2023/ko/days/day52.md23### Step 1: AWS 계정 만들기COMMENT
LOW2023/ko/days/day52.md27### Step 2: IAM 설정COMMENT
LOW2023/ko/days/day52.md31### Step 3: IAM 사용자 생성COMMENT
LOW2023/ko/days/day52.md35### Step 4: IAM 그룹 생성COMMENT
LOW2023/ko/days/day52.md39### Step 5: IAM Group에 권한 할당COMMENT
LOW2023/ko/days/day52.md43### Step 6: IAM 사용자 테스트COMMENT
LOW2023/ko/days/day55.md26### Step 1: IAM 역할 만들기COMMENT
LOW2023/ko/days/day55.md30### Step 2: CodePipeline 파이프라인 생성COMMENT
LOW2023/ko/days/day55.md34### Step 3: 코드 변경 테스트 및 배포COMMENT
LOW2023/ko/days/day50.md5## Step 1: AWS 웹사이트로 이동COMMENT
LOW2023/ko/days/day50.md10## Step 2: AWS 계정 생성COMMENT
LOW2023/ko/days/day50.md16## Step 3: 계정 정보 제공COMMENT
LOW2023/ko/days/day50.md23## Step 4: 결제 정보 제공COMMENT
LOW2023/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