Summary
The repository currently uses a Repobeats statistics card to display repository activity. However, the embedded statistics appear to be stale and do not reflect the repository's recent development activity.
This may give contributors and visitors an inaccurate impression of the project's maintenance and activity.
Current embedded stats:

Problem
- The Repobeats card has not updated despite recent repository activity.
- Repository metrics shown in the card are outdated.
- Visitors may assume the project is less active than it actually is.
Proposed Solution
Replace Repobeats with a more actively maintained and reliable GitHub statistics service, such as:
- GitHub Readme Activity Graph
- GitHub Readme Stats
- Shields.io (for repository metrics)
These alternatives are widely adopted in the open-source community and tend to provide more consistent updates.
Alternatives Considered
- GitHub Readme Activity Graph
- GitHub Readme Stats
- Shields.io (for repository metrics)
Additional Context
Repobeats appears to cache repository data for extended periods, causing the displayed statistics to remain outdated even after significant development activity. Replacing it with a more actively maintained alternative would ensure that repository metrics remain current.
Summary
The repository currently uses a Repobeats statistics card to display repository activity. However, the embedded statistics appear to be stale and do not reflect the repository's recent development activity.
This may give contributors and visitors an inaccurate impression of the project's maintenance and activity.
Current embedded stats:
Problem
Proposed Solution
Replace Repobeats with a more actively maintained and reliable GitHub statistics service, such as:
These alternatives are widely adopted in the open-source community and tend to provide more consistent updates.
Alternatives Considered
Additional Context
Repobeats appears to cache repository data for extended periods, causing the displayed statistics to remain outdated even after significant development activity. Replacing it with a more actively maintained alternative would ensure that repository metrics remain current.