---

Short Name	Title	Category	Principle	Keywords
RSFC-01-1	Software has a persistent identifier which resolves	Findable, Reusable	F1 R3	Identifier resolve, Test
RSFC-01-2	Software metadata refers to the software identifier	Findable, Reusable	F1 R3	Identifier, Test
RSFC-01-3	Software identifier follows a common schema	Findable, Reusable	F1 R3	Schema, Test
RSFC-03-1	Software has releases	Findable	F1 F1.2	Releases, Test
RSFC-03-2	Releases have an id and version number	Findable	F1 F1.2	Number version, Identifier, Test
RSFC-03-3	Release versions follow a community established naming convention	Findable	F1 F1.2	Convention, Test
RSFC-03-4	Release identifiers follow the same scheme	Findable	F1 F1.2	Schema, Identifiers, Test
RSFC-03-5	Last release consistency	Findable	F1 F1.2	Version number, Release, Test
RSFC-03-6	Version number in metadata	Findable	F1 F1.2	Version number, Release, Test
RSFC-04-1	Software metadata exists	Findable, Reusable	F2 R1 R3	Metadata, Test
RSFC-04-2	A README file exists	Findable, Reusable	F2 R1 R3	Readme, Test
RSFC-04-3	Title and description are declared	Findable, Reusable	F2 R1 R3	Title, Description, Test
RSFC-04-4	Software has descriptive metadata	Findable, Reusable	F2 R1 R3	Metadata, Description, Test
RSFC-04-5	There is a codemeta file	Findable, Reusable	F2 R1 R3	Codemeta, Test
RSFC-05-1	A repostatus badge exists	Findable, Reusable	F2 R1 R3	Badsge, Test
RSFC-05-2	Contact and/or support metadata exists	Findable, Reusable	F2 R1 R3	Contact, Support metadata, Test
RSFC-05-3	Software documentation	Findable, Reusable	F2 R1 R3	Documentation, Test
RSFC-06-1	Authors are declared	Findable, Reusable	F2 R3	Author, Contributor, Test
RSFC-06-2	Contributors are declared	Findable, Reusable	F2 R3	Author, ORCID, Test
RSFC-06-3	Authors have an ORCID	Findable, Reusable	F2 R3	Author, Rol, Test
RSFC-06-4	Authors have roles	Findable, Reusable	F2 R3	Author, Rol, Test
RSFC-07-1	There is an identifier in README or CITATION.cff	Findable, Reusable	F3 R3	Identifier, Readme, Citation, Test
RSFC-07-2	Software identifier resolves to software	Findable, Reusable	F3 R3	Identifier, Test
RSFC-08-1	Metadata record in Software Heritage or Zenodo	Findable, Accessible, Reusable	F4 A2 R3	Zenodo, Software Heritage, Test
RSFC-09-1	Repository is from Github/Gitlab	Accessible, Reusable	A1 A1.1 A1.2 R3	URL, Github, Test
RSFC-12-1	There is an article citation or reference publication	Interoperable	I2	Citation, Reference Publication, Test
RSFC-13-1	Dependencies are declared	Reusable	R1 R2	Dependencies, Test
RSFC-13-2	Installation instructions exist	Reusable	R1 R2	Installation instructions, Test
RSFC-13-3	Dependencies have version numbers	Reusable	R1 R2	Dependencies, Number version, Test
RSFC-13-4	Dependencies are machine-readable	Reusable	R1 R2	Machine-readable, Test
RSFC-14-1	Presence of tests in source code repository	Reusable	R1	Repository, Test
RSFC-14-2	There are actions to automate tests	Reusable	R1	Github actions, Workflows, Test
RSFC-15-1	Software has license	Reusable	R1.1	License, Test
RSFC-15-2	License is SPDX compliant	Reusable	R1.1	License, SPDX, Test
RSFC-16-1	License referenced in metadata files	Reusable	R1.1	Metadata, Codemeta, Citation, Repository, Test
RSFC-17-1	Repository active	Reusable	R1.2	Active, Repository, Test
RSFC-17-2	Commit history	Reusable	R1.2	Active, Repository, Test
RSFC-17-3	Commits are linked to issues	Reusable	R1.2	Active, Repository, Test
RSFC-18-1	Repository has citation	Interoperable	I2	Citation, Readme, Test
RSFC-19-1	Repository has continuous integration workflows	Reusable	R3	Continuous integracion, Workflow, Test
RSFC-20-1	Repository has an issue tracker			Issue tracker, Repository, Test

---

Short Name	Title	Category	Principle	Keywords

---

Name	Title	Keywords
FAIR4RS Benchmark	General Benchmark for RSFC	General Benchmark, Benchmark, Default, RSFC, Quality checks