# Documentation Files in the Root of the DeusData/codebase-memory-mcp Repository > Discover documentation files in the root of DeusData/codebase-memory-mcp. Find Markdown guides on project overview, contributions, security, and legal governance. - Repository: [Martin Vogel/codebase-memory-mcp](https://github.com/DeusData/codebase-memory-mcp) - Tags: documentation - Published: 2026-07-14 --- **The DeusData/codebase-memory-mcp repository contains eight documentation files in its root directory, including six Markdown guides and two text files that cover project overview, contribution workflows, security policies, and legal governance.** The **DeusData/codebase-memory-mcp** project maintains its primary documentation at the repository root, following standard open-source conventions for discoverability. These **root documentation files** serve as the central knowledge base for developers, contributors, and security researchers interacting with the codebase. Understanding the purpose and content of each file enables efficient onboarding and ensures compliance with project standards and licensing requirements. ## Core Project Documentation The repository's top-level directory includes several Markdown files that provide essential information for users and contributors. These files explain how to build the project, submit changes, and engage with the community. ### README.md The **[`README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/README.md)** file serves as the entry point for anyone discovering the repository. Located at the repository root, this file explains the purpose of codebase-memory-mcp, provides basic usage instructions, and includes building instructions along with quick-start commands. Developers should consult this file first when attempting to understand the project's functionality or set up a local development environment. ### CONTRIBUTING.md The **[`CONTRIBUTING.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/CONTRIBUTING.md)** file details the complete workflow for submitting changes to the project. This documentation covers the pull-request process, code style requirements, testing procedures, and linting expectations. Contributors must review this file before submitting patches to ensure their submissions meet the project's quality standards and review criteria. ### SECURITY.md The **[`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md)** file outlines the security policy and vulnerability disclosure process for the codebase-memory-mcp project. This document specifies how to responsibly disclose security vulnerabilities and lists the responsible security contacts. Researchers and users who discover potential security issues should follow the procedures outlined in this file rather than opening public issues. ## Governance and Legal Files Beyond technical documentation, the root directory contains several files governing community interaction and legal compliance. ### CODE_OF_CONDUCT.md The **[`CODE_OF_CONDUCT.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/CODE_OF_CONDUCT.md)** file establishes community standards and expected behavior for all participants in the project. This document defines acceptable conduct for contributors, maintainers, and users engaging with the repository through issues, pull requests, and discussions. ### MAINTAINERS.md The **[`MAINTAINERS.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/MAINTAINERS.md)** file provides a list of current project maintainers and their specific responsibilities within the codebase-memory-mcp organization. This documentation helps contributors understand who to contact for specific types of questions or approvals. ### THIRD_PARTY.md The **[`THIRD_PARTY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/THIRD_PARTY.md)** file enumerates external libraries and resources bundled with the project, ensuring compliance with their respective licenses. This attribution file is critical for legal compliance and transparency regarding dependencies distributed with the codebase. ### LICENSE The **`LICENSE`** file (plain text format) contains the full open-source license text (Apache-2.0) governing the repository. This file defines the legal terms under which users can use, modify, and distribute the codebase-memory-mcp software. ### DCO The **`DCO`** file (plain text format) contains the Developer Certificate of Origin, serving as a contributor agreement. This document establishes that contributors have the right to submit their code and understand that the project is licensed under the Apache-2.0 license. ## Accessing Documentation in the Repository All documentation files reside directly in the top-level directory of the repository. Users can access these files directly through the GitHub web interface or clone the repository to view them locally. ```bash # Clone the repository to access all documentation locally git clone https://github.com/DeusData/codebase-memory-mcp.git cd codebase-memory-mcp # List all documentation files in the root ls -la *.md LICENSE DCO ``` When browsing the repository on GitHub, these files render automatically as formatted HTML, making them easily readable without downloading the entire codebase. ## Summary - The **DeusData/codebase-memory-mcp** repository contains eight documentation files in its root directory. - **Markdown files** include [`README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/README.md), [`CONTRIBUTING.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/CONTRIBUTING.md), [`CODE_OF_CONDUCT.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/CODE_OF_CONDUCT.md), [`MAINTAINERS.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/MAINTAINERS.md), [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md), and [`THIRD_PARTY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/THIRD_PARTY.md). - **Text files** include `LICENSE` (Apache-2.0) and `DCO` (Developer Certificate of Origin). - These files cover project usage, contribution guidelines, community standards, security disclosure, and legal compliance. - All documentation is located at the repository root for immediate visibility and standard open-source discoverability. ## Frequently Asked Questions ### What is the purpose of the README.md file in the codebase-memory-mcp repository? The [`README.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/README.md) file serves as the primary entry point for the repository, providing a general project description, basic usage instructions, building guidelines, and quick-start commands. According to the DeusData/codebase-memory-mcp source code, this file explains the project's purpose and should be the first document consulted by new users or contributors. ### How do I report security vulnerabilities for the codebase-memory-mcp project? Security vulnerabilities should be reported according to the procedures outlined in the [`SECURITY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/SECURITY.md) file located in the repository root. This file contains the security policy, vulnerability disclosure process, and contact information for responsible security personnel, ensuring that sensitive issues are handled privately rather than through public issue trackers. ### What is the DCO file in the root directory of codebase-memory-mcp? The `DCO` file contains the Developer Certificate of Origin, which is a contributor agreement that establishes the legal rights of contributors to submit their code. As implemented in DeusData/codebase-memory-mcp, this file indicates that contributors certify they have the right to submit their contributions under the Apache-2.0 license that governs the repository. ### Where can I find third-party licensing information for this project? Third-party licensing information and attribution are documented in the [`THIRD_PARTY.md`](https://github.com/DeusData/codebase-memory-mcp/blob/main/THIRD_PARTY.md) file at the repository root. This file enumerates external libraries and resources bundled with the project, ensuring compliance with their respective licenses and providing transparency regarding dependencies distributed with the codebase-memory-mcp software.