FAIR Compliance Dashboard
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 20/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- github
- Domain
- documentation
Research direction
This issue is an automated FAIR compliance dashboard that reports repository files and links to Codefair actions. Start with the linked dashboard documentation to understand its purpose; the payload names no source files or tests. There is no code change specified, and closing the issue can restore the dashboard if needed.
Written by the indexing model from the issue text.
Description
Check the FAIRness of your software
This issue is your repository's dashboard for all things FAIR. Keep it open as making and keeping software FAIR is a continuous process that evolves along with the software. You can read the documentation to learn more.
README ✔️
A README.md file was found at within your repository.
LICENSE ❗
Your LICENSE file needs verification. This can happen when:
- Your license content was modified and we need you to confirm the license type
- You're using a license that GitHub doesn't recognize but may still be a valid SPDX license
- You're using a truly custom license
[!NOTE]
If you plan to archive on Zenodo, you'll need to select a license from the SPDX license list. Custom licenses are not currently supported by Zenodo's API.
Click the "Edit license" button below to confirm your license type (select from the dropdown and choose "Keep existing content") or provide a custom license title.
Metadata ❌
To make your software FAIR, a CITATION.cff and codemeta.json are expected at the root level of your repository. These files are not found in the repository. If you would like Codefair to add these files, click the "Add metadata" button below to go to our interface for providing metadata and generating these files.
FAIR Software Release ❌
To make your software FAIR, it is necessary to archive it in an archival repository like Zenodo every time you make a release. When you are ready to make your first release, click the "Create release" button below to easily create a FAIR release where your metadata files are updated (including with a DOI) before creating a GitHub release and archiving it on Zenodo.
Additional Recommendations
Although these files are not part of the core FAIR compliance checks, Codefair recommends including them to improve project governance, community engagement, and contributor experience:
CONTRIBUTING.md ✔️
This file helps communicate contribution processes and gives contributors clear guidelines placed at the repo root (or in docs/ or .github/), saving time and reducing rework. It surfaces automatically on pull requests, issues, and the repository's Contribute page to guide contributors at every step.
CODE_OF_CONDUCT.md ✔️
Defines clear standards for respectful engagement and shows a welcoming, inclusive community by outlining expectations and procedures for handling abuse. When placed at the repo root (or in docs/ or .github/), CODE_OF_CONDUCT.md surfaces in the repository's community profile and contributor pages to guide behavior at every step.
Last updated Nov 2 2026, 10:42:10 (timezone: America/Los_Angeles)
PLEASE NOTE: deleting this issue will require reinstalling the Codefair GitHub App, but closing the issue will allow you to restore the FAIR Compliance Dashboard by reopening the issue.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 0
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 4
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Similar issues
-
Contribute FeedbackOpen
Difficulty 1/5 Under an hour Newbie friendliness 67/100
MicrosoftDocs/WSL#2654 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
hibernate/hibernate-reactive#4485 ·
Maintainers usually reply within 1 day
-
vuln:LOW
Difficulty 1/5 Under an hour Newbie friendliness 63/100
curl/curl-www#679 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
mxschmitt/awesome-playwright#285 ·
Maintainers usually reply within 19 days
-
area/access-management Frontend onboarding candidate :handshake:
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Altinn/altinn-auth#4941 ·
Maintainers usually reply within 1 day