An automated bot that analyzes repository metadata quality and creates issues with improvement suggestions.
Part of the CodeMetaSoft project to improve research software metadata quality.
If you received an issue from this bot, it means your repository's metadata was automatically analyzed and some improvements were detected on the main default branch.
The issue contains:
- Pitfalls: Critical metadata issues that should be fixed
- Warnings: Metadata improvements that are recommended
- Suggestions: Specific recommendations on how to fix each issue
- Codemeta.json generation: if your repo does not contain any
codemeta.jsonfile, the bot suggests one.
### [P002](https://w3id.org/rsmetacheck/catalog/#P002)
**Evidence:** P002 detected: LICENSE file contains unreplaced template placeholders
**Suggestion:** Update the copyright section with accurate names, organizations, and the current year. Personalizing this section ensures clarity and legal accuracy.Fix the identified issues and close the issue with a comment explaining what you fixed. Your improvements help your software become more discoverable and citable!
Feel free to comment on the issue. We're happy to discuss the suggestions and help clarify what's needed.
Simply comment "unsubscribe" on the issue and we'll remove your repository from future analysis.
This bot uses rsmetacheck, which analyzes:
- Software metadata completeness
- Citation and documentation quality
- Repository structure and best practices
The bot does not:
- Modify your code or files
- Make pull requests
- Have access to your repository secrets
pip install rsmetacheck-botuv add rsmetacheck-bot- CodeMetaSoft Project - About the initiative
- rsmetacheck - The analysis tool
- Citation File Format - How to add CITATION.cff
See CONTRIBUTING.md for setup and usage instructions.
Project storage policy: the repo-centric layout and migration rules are described in docs/output_storage.rst.
The pipeline is config driven: one JSON file defines the repository list, issue message, inline opt-outs, and output layout.
Supported platforms:
- ✅ GitHub.com
- ✅ Gitlab.com
The bot is handling self-hosted gitlab platform but requires providing a token to this server (and not gitlab.com).
Use these commands when validating the bot without creating live issues:
- Legacy snapshot conversion
uv run sw-metadata-bot convert-legacy outputs/legacy_snapshot --target-root outputs/convertedThis converts a legacy snapshot tree into the current repo-centric layout without publishing anything.
- Fresh dry-run analysis from scratch
uv run sw-metadata-bot run-analysis --config-file config.json --snapshot-tag 202603This writes analysis outputs and run reports, but remains dry-run and does not create issues.
- Simulated publish review
uv run sw-metadata-bot simulate-publish --analysis-root outputs/batch-a/202603This replays the analysis decisions with a fake issue client so you can review the generated issue bodies and opt-out logic without spamming real repositories.
Avoid the live
publishcommand unless you explicitly want to create or update real repository issues.
See LICENSE file.