Skip to content

RSFC_REPORT.md

Latest commit

 

History

History
681 lines (576 loc) · 36.1 KB

RSFC_REPORT.md

File metadata and controls

681 lines (576 loc) · 36.1 KB
Raw

Quality Assessment for rsfc v0.1.6

An automated assessment of the rsfc tool based on the EVERSE software quality indicators, run on 2026-07-02.

General Information

Summary

  • Passed (true): 34
  • Failed (false): 7
  • Errors (error): 0

Results Table

TEST ID Short Description Output
RSFC-01-1 There is an identifier and it resolves true
RSFC-01-2 There is an identifier in the metadata files true
RSFC-01-3 There is an identifier and it follows a common schema true
RSFC-03-1 The software has releases true
RSFC-03-2 Releases have version and identifier true
RSFC-03-3 Release versions follow SemVer or CalVer true
RSFC-03-4 Release identifiers follow the same scheme true
RSFC-03-5 Last release version corresponds to version in package file true
RSFC-03-6 There is a version number stated in metadata files true
RSFC-04-1 Metadata files exist true
RSFC-04-2 There is a README file true
RSFC-04-3 Title and description are declared true
RSFC-04-4 There is descriptive metadata true
RSFC-04-5 There is a codemeta file true
RSFC-05-1 There is a repostatus badge in the README file true
RSFC-05-2 Contact and support metadata exists true
RSFC-05-3 Software documentation exists true
RSFC-06-1 Authors are declared true
RSFC-06-2 Contributors are declared false
RSFC-06-3 Authors have an ORCID assigned false
RSFC-07-1 There is an identifier in README or CITATION true
RSFC-07-2 Software identifier resolves and links back to software true
RSFC-08-1 Metadata record is found in SWHeritage or Zenodo true
RSFC-09-1 Repository is from Github or Gitlab true
RSFC-12-1 There is an article citation or reference publication false
RSFC-13-1 Dependencies are declared true
RSFC-13-2 There are installation instructions true
RSFC-13-3 Dependencies have version numbers false
RSFC-13-4 Dependencies are in a machine-readable format true
RSFC-14-1 Tests are provided true
RSFC-14-2 There are actions to automate tests false
RSFC-15-1 There is a license true
RSFC-15-2 License is in SPDX format true
RSFC-16-1 License is referenced in metadata files true
RSFC-17-2 Repository has a commit history true
RSFC-17-3 Commits are linked to issues false
RSFC-18-1 There are citations true
RSFC-19-1 Repository has continuous integration workflows true
RSFC-20-1 Repository has an issue tracker true
RSFC-21-1 Repository has contribution guidelines false
RSFC-22-1 Software offers a container file to run it true

Detailed Results by Indicator

archived_in_software_heritage

Metadata record in Software Heritage or Zenodo

descriptive_metadata

Version number in metadata

Metadata exists

  • Test ID: https://w3id.org/rsfc/test/RSFC-04-1
  • Result: true
  • Process: Searches for codemeta, citation and package files in the repository
  • Evidence: Found CITATION.cff, codemeta.json, package_file in the repository
  • Suggestions: N/A

There are title and description

Software has descriptive metadata

There is a codemeta file

  • Test ID: https://w3id.org/rsfc/test/RSFC-04-5
  • Result: true
  • Process: Searches for a codemeta.json file in the repository
  • Evidence: A codemeta.json file was found in the root of the repository
  • Suggestions: N/A

Authors are declared

Contributors are declared

Authors have an ORCID

has_contribution_guidelines

Repository has contribution guidelines

  • Test ID: https://w3id.org/rsfc/test/RSFC-21-1
  • Result: false
  • Process: Checks if there are contribution guidelines either in the README file or if there is a CONTRIBUTING.md file
  • Evidence: Could not find contribution guidelines in the repository
  • Suggestions: If you want to properly keep track of the colaborations your project receives to ensure its quality and fiability, you should add some contribution guidelines so the colaborators know how you want contributions to be made

has_releases

Software has releases

Releases have an id and version number

  • Test ID: https://w3id.org/rsfc/test/RSFC-03-2
  • Result: true
  • Process: Checks if all of the releases have an identifier and a version
  • Evidence: All of the releases have an id and a version
  • Suggestions: N/A

Release identifiers follow the same scheme

  • Test ID: https://w3id.org/rsfc/test/RSFC-03-4
  • Result: true
  • Process: Checks if all of the version identifiers follow the same scheme
  • Evidence: All of the releases URLs follow the same scheme
  • Suggestions: N/A

Last release consistency

  • Test ID: https://w3id.org/rsfc/test/RSFC-03-5
  • Result: true
  • Process: Checks if the latest release tag matches the version stated in the codemeta or package files of the repository
  • Evidence: Latest release matches the latest version stated in the metadata files
  • Suggestions: N/A

persistent_and_unique_identifier

There is an identifier and resolves

There is an identifier associated with the software

  • Test ID: https://w3id.org/rsfc/test/RSFC-01-2
  • Result: true
  • Process: Searches for an identifier in the CITATION.cff, codemeta.json and README files
  • Evidence: An identifier was found in CITATION.cff, README.md, codemeta.json.
  • Suggestions: N/A

Software identifier follows a proper schema

  • Test ID: https://w3id.org/rsfc/test/RSFC-01-3
  • Result: true
  • Process: Checks if the identifiers associated with the software follow any of these schemas: DOI, URN, GITHUB and SWHID
  • Evidence: All of the identifiers detected follow a common schema
  • Suggestions: N/A

There is an identifier in README or CITATION.cff

Software identifier resolves to software

  • Test ID: https://w3id.org/rsfc/test/RSFC-07-2
  • Result: true
  • Process: Checks if the identifier found in the README file or metadata files (i.e. codemeta.json, CITATION.cff) resolves to a page that links back to the software repository
  • Evidence: The landing page of the software's identifier https://doi.org/10.5281/zenodo.16531481 links back to the software repository
  • Suggestions: N/A

repository_workflows

There are actions to automate tests

Repository has workflows

requirements_specified

Dependencies are declared

Dependencies have version numbers

There is a dependencies machine-readable file

software_has_citation

There is an article citation or reference publication

  • Test ID: https://w3id.org/rsfc/test/RSFC-12-1
  • Result: false
  • Process: Searches for an article citation or a reference publication in the codemeta and citation files
  • Evidence: Could not find neither a reference publication or citation to an article in the repository
  • Suggestions: You should include other forms of citation like article citations and reference publications in your software's metadata. More information at https://everse.software/RSQKit/creating_good_readme

Repository has citation

software_has_documentation

There is a README

  • Test ID: https://w3id.org/rsfc/test/RSFC-04-2
  • Result: true
  • Process: Searches for a README file in the repository
  • Evidence: There is a README file in the repository
  • Suggestions: N/A

There is contact and/or support metadata

Software documentation

There are installation instructions

software_has_license

Software has license

License is SPDX compliant

License referenced in metadata files

  • Test ID: https://w3id.org/rsfc/test/RSFC-16-1
  • Result: true
  • Process: Searches for licensing information in the codemeta, CITATION.cff and package files if they exist
  • Evidence: License information was found in codemeta (MIT), CITATION.cff (MIT), package (MIT)
  • Suggestions: N/A

software_has_tests

Presence of tests in repository

  • Test ID: https://w3id.org/rsfc/test/RSFC-14-1
  • Result: true
  • Process: Searches for files and/or directories that mention test in their names. Also, ignores doc and docs directories
  • Evidence: Files and/or directories that mention test were found at:
    • tests
    • tests/test_main.py
  • Suggestions: N/A

software_is_containerized

Software is containerized

support_issue_tracking

Repository has an issue tracker

  • Test ID: https://w3id.org/rsfc/test/RSFC-20-1
  • Result: true
  • Process: Checks if there is an issue tracker in the repository.
  • Evidence: There is an issue tracking system in the repository but it isn't stated in any of the files
  • Suggestions: N/A

version_control_use

There is a repostatus badge

Repository is from Github/Gitlab

  • Test ID: https://w3id.org/rsfc/test/RSFC-09-1
  • Result: true
  • Process: Checks if the URL provided is indeed a Github or Gitlab repository
  • Evidence: URL provided is a Github or Gitlab repository
  • Suggestions: N/A

Commit history

Commits are linked to issues

  • Test ID: https://w3id.org/rsfc/test/RSFC-17-3
  • Result: false
  • Process: Checks if there is at least one of the existing issues (opened or closed) referenced in any of the commits made in the default branch of the repository
  • Evidence: There is not any commits linked to any issues in the repository
  • Suggestions: It is good practice to indicate in your commits which issues you are targeting or solving

versioning_standards_use

Release versions follow a community established convention

  • Test ID: https://w3id.org/rsfc/test/RSFC-03-3
  • Result: true
  • Process: Checks if all of the releases versions follow the SemVer or CalVer versioning standards
  • Evidence: All of the releases follow a versioning standard
  • Suggestions: N/A