Software provenance

FRSM-17: The software includes provenance information that describe the development of the software. Test: 1) The software source code repository / forge includes a commit history (Essential). 2) The software source code repository links commits to issues / tickets (Important). 3) The software project uses other tools to capture detailed machine readable provenance information (Useful). Notes: - It is hard to check the relevance / correctness of this information, but it is possible to automatically check for existence. - As a type of metadata this overlaps with the metadata called for in guiding principles F2 and F4.

Principle: R

Rationale: Good provenance metadata clarifies the origins and intent behind the development of the software, and establishes authenticity and trust.

FAIR Metrics: R1.2