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/ctlearn-project/ctlearn
Analysis Date: 2026-05-22
sw-metadata-bot version: 0.4.3
RSMetacheck version: 0.3.1
🔴 Pitfalls (2)
Evidence: P004 detected: metadata files README property points to homepage/wiki instead of README file: https://ctlearn.readthedocs.io
Suggestion: Update the README property so it points directly to your actual README file (https://raw.githubusercontent.com/ctlearn-project/ctlearn/main/README.rst) instead of your homepage.
Evidence: P014 detected: metadata files Identifier uses bare DOI instead of full URL: '10.5281/zenodo.3342952'
Suggestion: You should include the full DOI URL form in your metadata (e.g., https://doi.org/10.5281/zenodo.3342952)
⚠️ Warnings (3)
Evidence: W001 detected: codemeta.json contains software requirements without versions: Python 3, TensorFlow 2, astropy, astropy, scikit-learn, scikit-learn, ctapipe, DL1DataHandler, numba, numba, NumPy, NumPy, PyYAML, PyYAML, PyDot, PyDot, Pandas, Pandas, tensorboard, setuptools, sphinx, sphinx_rtd_theme
Suggestion: Add version numbers to your dependencies. This provides stability for users and allows reproducibility across different environments.
Evidence: W002 detected: metadata files dateModified '2025-03-21T00:00:00' is outdated compared to repository date '2026-04-07T09:50:21'
Suggestion: The data in the metadata file should be updated to be aligned with the date of the latest release (2026-04-07T09:50:21).
Evidence: W004 detected: metadata files Programming languages without versions: Python 3
Suggestion: Include version numbers for each programming language used. Defining these helps ensure reproducibility and compatibility across systems.
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/ctlearn-project/ctlearn
Analysis Date: 2026-05-22
sw-metadata-bot version: 0.4.3
RSMetacheck version: 0.3.1
🔴 Pitfalls (2)
P004
Evidence: P004 detected: metadata files README property points to homepage/wiki instead of README file: https://ctlearn.readthedocs.io
Suggestion: Update the README property so it points directly to your actual README file (https://raw.githubusercontent.com/ctlearn-project/ctlearn/main/README.rst) instead of your homepage.
P014
Evidence: P014 detected: metadata files Identifier uses bare DOI instead of full URL: '10.5281/zenodo.3342952'
Suggestion: You should include the full DOI URL form in your metadata (e.g., https://doi.org/10.5281/zenodo.3342952)
W001
Evidence: W001 detected: codemeta.json contains software requirements without versions: Python 3, TensorFlow 2, astropy, astropy, scikit-learn, scikit-learn, ctapipe, DL1DataHandler, numba, numba, NumPy, NumPy, PyYAML, PyYAML, PyDot, PyDot, Pandas, Pandas, tensorboard, setuptools, sphinx, sphinx_rtd_theme
Suggestion: Add version numbers to your dependencies. This provides stability for users and allows reproducibility across different environments.
W002
Evidence: W002 detected: metadata files dateModified '2025-03-21T00:00:00' is outdated compared to repository date '2026-04-07T09:50:21'
Suggestion: The data in the metadata file should be updated to be aligned with the date of the latest release (2026-04-07T09:50:21).
W004
Evidence: W004 detected: metadata files Programming languages without versions: Python 3
Suggestion: Include version numbers for each programming language used. Defining these helps ensure reproducibility and compatibility across systems.
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.