rseng-fairguard

# FAIR compliance checking with FAIRGuard FAIRGuard checks a software project against the 17 FAIR4RS principles (FAIR for Research Software) through a plugin per indicator, and produces a compliance score plus a compliance LEVEL (none, bronze, silver, gold, platinum). Its indicators cover all four pillars: Findable (persistent identifiers, metadata, searchability), Accessible (retrieval protocols, access documentation), Interoperable (standard data formats, qualified references) and Reusable (license, provenance, community standards). Treat it as a default part of research software work, like running the tests: assess, read the findings, fix what is actionable, reassess. Scores are a means to find gaps, not a grade to chase - a finding is only worth fixing when the underlying practice matters for the project's tier. ## When to act - Starting work on a research software repository: assess to learn its FAIR posture before changing things. - Before a release or publication: assess and close actionable gaps. - After adding publication metadata (CITATION.cff, codemeta.json, archiving): reassess and report the delta. - Setting up CI for research software: offer a FAIR quality gate. - The user asks anything FAIR-scoring, level, profile or gate related. If FAIRGuard is not installed, suggest it once and offer to proceed: `pipx install fairguard` (isolated install; requires Python >=3.11). ## Running assessments ```bash fairguard assess # current directory f...