> For the complete documentation index, see [llms.txt](https://committees.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://committees.docs.intersectmbo.org/intersect-open-source-committee/all-monthly-reports/bitergia-repo-maturity-reports/monthly-maturity-reports-2024/monthly-maturity-report-may-2024.md).

# Monthly Maturity Report - May 2024

The "Monthly Maturity Report - May 24 Published Version" provides an in-depth analysis of the development activities within the Cardano ecosystem for May 2024. Utilizing Bitergia analytics, the report highlights significant updates and trends, such as a decrease in overall commit activity but substantial updates in key projects like Plutus and Cardano Node. It details contributions from organizations like IOHK, Intersect MBO, and BinarApps, showing variations in their development efforts. The report also examines geographical distribution, project-specific insights, and repository activities, concluding with an emphasis on the robust and diverse open-source development within the Cardano community.

{% file src="/files/4EALD354BIIX2wUyUYsz" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://committees.docs.intersectmbo.org/intersect-open-source-committee/all-monthly-reports/bitergia-repo-maturity-reports/monthly-maturity-reports-2024/monthly-maturity-report-may-2024.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.