ARTIST-Association / ARTIST-Association/PAINT

FAIR Compliance Dashboard

Open
#132 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
8
Forks
0
Avg merge
4d 26m
Merged PRs (30d)
2

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](https://docs.codefair.io/docs/dashboard.html) to learn more.

## README ✔️

A `README.md` file was found at within your repository.

[![Edit README](https://img.shields.io/badge/Edit_README-0ea5e9.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/edit/readme)

## LICENSE ✔️

A `LICENSE` file is found at the root level of the repository.

[![License](https://img.shields.io/badge/Edit_License-0ea5e9.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/edit/license)

## 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.

[![Metadata](https://img.shields.io/badge/Add_Metadata-dc2626.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/edit/code-metadata)

## 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.

[![Create Release on Zenodo](https://img.shields.io/badge/Create_Release_on_Zenodo-dc2626.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/release/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.

[![CONTRIBUTING.md](https://img.shields.io/badge/Edit_CONTRIBUTING-0ea5e9.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/edit/contributing)

### 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.

[![CODE_OF_CONDUCT.md](https://img.shields.io/badge/Edit_CODE_OF_CONDUCT-0ea5e9.svg)](https://codefair.io/dashboard/ARTIST-Association/PAINT/edit/code-of-conduct)

Last updated Aug 31 2026, 13:30:38 (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.

Contributor guide

Open the contributing guide

Research direction

Review the linked Codefair dashboard documentation and inspect the repository root for the missing CITATION.cff and codemeta.json files. Use the linked Codefair metadata interface to determine the required project information, then review the Zenodo release workflow. Done means the metadata files are present and a FAIR release is archived.

Written by the indexing model from the issue text.

Assessment

Tech stack
github
Domain
documentation, release
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.