You are part of the Software Understanding metadata quality initiative beta analysis. This initiative is meant to test the use of a bot to monitor the quality of metadata in software repositories.
This automated issue includes:
- Detected metadata pitfalls and warnings
- A suggested codemeta.json when no codemeta.json was detected
- Suggestions for fixing each issue
Context
This analysis is performed by the CodeMetaSoft project to help improve research software metadata quality.
This is a first initiative aimed at identifying and reporting metadata quality issues across research software repositories.
At this stage, we only provide diagnostics and recommendations.
In future iterations, we plan to propose automated fixes for the detected issues to further simplify the improvement process and reduce manual effort.
Each pitfall and warning is identified by a unique code (e.g. P001 for pitfalls, W004 for warnings) that corresponds to specific metadata quality issues.
You can find more details about these checks and how to address them in the RSMetacheck catalog.
Metadata Quality Report
Repository: https://github.com/FairRootGroup/FairMQ
Analysis Date: 2026-05-22
sw-metadata-bot version: 0.4.3
RSMetacheck version: 0.3.1
🔴 Pitfalls (2)
Evidence: P001 detected: codemeta.json version 'master' does not match release version '1.10.1'
Suggestion: Ensure the version in your metadata matches the latest official release (1.10.1). Keeping these synchronized avoids confusion for users and improves reproducibility.
Evidence: P006 detected: codemeta.json License points to local file instead of license name: './COPYRIGHT'
Suggestion: You need to replace local file paths with recognized SPDX license identifiers, such as MIT or GPL-3.0-only in URL form. This ensures your license can be correctly detected by automated tools.
This report was generated automatically by sw-metadata-bot on your main default branch.
If you're not interested in participating, please comment "unsubscribe" and we will remove your repository from our list.
If you would like the pitfalls and warnings to be fixed automatically, please comment "auto-fix" and we will prioritize adding this feature in future iterations.
You are part of the Software Understanding metadata quality initiative beta analysis. This initiative is meant to test the use of a bot to monitor the quality of metadata in software repositories.
This automated issue includes:
Context
This analysis is performed by the CodeMetaSoft project to help improve research software metadata quality.
This is a first initiative aimed at identifying and reporting metadata quality issues across research software repositories.
At this stage, we only provide diagnostics and recommendations.
In future iterations, we plan to propose automated fixes for the detected issues to further simplify the improvement process and reduce manual effort.
Each pitfall and warning is identified by a unique code (e.g. P001 for pitfalls, W004 for warnings) that corresponds to specific metadata quality issues.
You can find more details about these checks and how to address them in the RSMetacheck catalog.
Metadata Quality Report
Repository: https://github.com/FairRootGroup/FairMQ
Analysis Date: 2026-05-22
sw-metadata-bot version: 0.4.3
RSMetacheck version: 0.3.1
🔴 Pitfalls (2)
P001
Evidence: P001 detected: codemeta.json version 'master' does not match release version '1.10.1'
Suggestion: Ensure the version in your metadata matches the latest official release (1.10.1). Keeping these synchronized avoids confusion for users and improves reproducibility.
P006
Evidence: P006 detected: codemeta.json License points to local file instead of license name: './COPYRIGHT'
Suggestion: You need to replace local file paths with recognized SPDX license identifiers, such as MIT or GPL-3.0-only in URL form. This ensures your license can be correctly detected by automated tools.
This report was generated automatically by sw-metadata-bot on your main default branch.
If you're not interested in participating, please comment "unsubscribe" and we will remove your repository from our list.
If you would like the pitfalls and warnings to be fixed automatically, please comment "auto-fix" and we will prioritize adding this feature in future iterations.