diff --git a/docs/features/repo-pages.md b/docs/features/repo-pages.md
index 7f38bec6..e077ae73 100644
--- a/docs/features/repo-pages.md
+++ b/docs/features/repo-pages.md
@@ -48,10 +48,20 @@ The charts on our repository pages offer a visual representation of key project
 - **Pull Request Dynamics**: Analyze pull request activity by the numbers of pull requests opened, closed, and merged. This provides an overview of collaboration efficiency and code review processes.
 - **Stars and Forks Over Time**: The number of stars and forks the project receives over time, illustrating the project's growth in popularity and its spread within the developer community.
 - **[Lottery Factor](../welcome/glossary.md#lottery-factor)**: This unique metric highlights the dependency on key contributors. A project is considered vulnerable if 2 or fewer contributors account for 50% or more of the project's contributions. This indicates a potential risk if one of these contributors leaves the project.
+- **[YOLO Coders](../welcome/glossary.md#yolo-coders)**: This metric identifies contributors who push changes directly to the default branch without creating a pull request or seeking community feedback. 
 - **Contributor Confidence**: This metric predicts the likelihood that users who star or fork a repository will return to make contributions. A higher confidence score indicates a greater probability of these users actively engaging with the repository.
 
 You can use the time range filter to view the number of stars and forks over different periods, such as the last 7 days, month, or the last year.
 
+#### Insights into YOLO Coders
+
+For small, independent side projects, this method can sometimes be acceptable due to the limited scope and impact of the changes. However, in larger projects with broader adoption, such practices can quickly lead to significant issues, including:
+
+- **Semantic Problems**: Lack of clear commit messages and structured development history can make it challenging to understand the evolution of the project.
+- **Communication Breakdowns**: Community members and collaborators may find it difficult to follow ongoing changes, align with the project’s direction, or contribute effectively.
+- **Security Risks**: Direct pushes to the default branch can introduce vulnerabilities. For instance, an accidental force push could erase critical history, or worse, a rogue commit could embed malicious code without detection.
+- **Quality Control**: By bypassing code reviews and automated checks, YOLO coders risk introducing bugs, breaking existing functionality, or compromising the project’s integrity.
+
 #### Insights into Contributor Confidence
 
 Contributor Confidence is a new metric that helps us understand the likelihood of someone who interacts with a repository (by starring or forking it) coming back to actually contribute code or other content.
diff --git a/docs/welcome/glossary.md b/docs/welcome/glossary.md
index 1cb972a0..afd6c7b9 100644
--- a/docs/welcome/glossary.md
+++ b/docs/welcome/glossary.md
@@ -66,4 +66,8 @@ PR Velocity tracks how quickly Pull Requests (PRs) are being merged in by identi
 
 ## Repository Insights
 
-The Repository Insights feature is a one-stop solution for understanding the pulse of your open-source projects and contributions. This feature is designed to provide a comprehensive view of your project's health and your individual contributions.
\ No newline at end of file
+The Repository Insights feature is a one-stop solution for understanding the pulse of your open source projects and contributions. This feature is designed to provide a comprehensive view of your project's health and your individual contributions.
+
+## YOLO Coders
+
+A “YOLO coder” is an individual owner, contributor, or maintainer who pushes changes directly to the default branch of a repository without creating a pull request or seeking any community feedback. This risky practice bypasses essential review and collaboration processes.
\ No newline at end of file