Jaime Arias Research Engineer CNRS, LIPN, Université Sorbonne Paris Nord November 4, 2025 THE GREAT LIBRARY OF SOURCE CODE Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 1 / 25
Engineer @ LIPN Ambassador @ Software Heritage Member @ Collège Codes Sources et Logiciels Chargé de mission Logiciels @ CNRS Sciences Info You can find me at: [email protected] https://www.jaime-arias.fr Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 1 / 25
over time projects may last decades the development history is key to its understanding Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 5 / 25
software artifacts must be properly archived make sure we can retrieve them (reproducibility) Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 6 / 25
software artifacts must be properly archived make sure we can retrieve them (reproducibility) Reference Research software artifacts must be properly referenced make sure we can identify them (reproducibility) Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 6 / 25
software artifacts must be properly archived make sure we can retrieve them (reproducibility) Reference Research software artifacts must be properly referenced make sure we can identify them (reproducibility) Describe Research software artifacts must be properly described make it easy to discover and reuse them (visibility) Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 6 / 25
software artifacts must be properly archived make sure we can retrieve them (reproducibility) Reference Research software artifacts must be properly referenced make sure we can identify them (reproducibility) Describe Research software artifacts must be properly described make it easy to discover and reuse them (visibility) Cite/Credit Research software artifacts must be properly cited (not the same as referenced!) to give credit to authors (evaluation!) Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 6 / 25
SOURCE CODE Collect, preserve and share all software source code Preserving our heritage, enabling better software and better science for all Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 7 / 25
SOURCE CODE Collect, preserve and share all software source code Preserving our heritage, enabling better software and better science for all Reference catalog find and reference all software source code Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 7 / 25
SOURCE CODE Collect, preserve and share all software source code Preserving our heritage, enabling better software and better science for all Reference catalog find and reference all software source code Universal archive preserve and share all software source code Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 7 / 25
SOURCE CODE Collect, preserve and share all software source code Preserving our heritage, enabling better software and better science for all Reference catalog find and reference all software source code Universal archive preserve and share all software source code Research infrastructure enable analysis of all software source code Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 7 / 25
intrinsic identifiers for software source code artifacts. SWHID has been officially adopted as ISO/IEC 18670:2025 on April 23, 2025. Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 9 / 25
intrinsic identifiers for software source code artifacts. SWHID has been officially adopted as ISO/IEC 18670:2025 on April 23, 2025. Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 9 / 25
intrinsic identifiers for software source code artifacts. SWHID has been officially adopted as ISO/IEC 18670:2025 on April 23, 2025. Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 9 / 25
LICENSE files 2 Save your code http://save.softwareheritage.org/ 3 Reference your work (full repository, specific version or code fragment) Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 10 / 25
and TeXLive, and it works out-of-the-box in Overleaf https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style Four dedicated entry types that reflect different levels of granularity: https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style Four dedicated entry types that reflect different levels of granularity: @software — for general references to computer software https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style Four dedicated entry types that reflect different levels of granularity: @software — for general references to computer software @softwaremodule — for citing a specific module within a larger software project https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style Four dedicated entry types that reflect different levels of granularity: @software — for general references to computer software @softwaremodule — for citing a specific module within a larger software project @softwareversion — for referencing a particular version of a software https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
and TeXLive, and it works out-of-the-box in Overleaf As of April 2022, it is integrated in the ACM article style Four dedicated entry types that reflect different levels of granularity: @software — for general references to computer software @softwaremodule — for citing a specific module within a larger software project @softwareversion — for referencing a particular version of a software @codefragment — for pinpointing a specific code fragment, such as an algorithm or a key function within a program or library https: //ctan.org/pkg/ biblatex-software Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 17 / 25
be already there !) 2 Trigger archival, use the updateswh browser extension, configure the webhooks 3 Get and use SWHIDs (full specification available online) 4 Cite software with biblatex-software package from CTAN Overleaf ACMART template available 5 Curated deposit in SWH via HAL, see for example: LinBox, SLALOM, Givaro, NS2DDV, SumGra, Coq proof, ... 6 Extracting all the software products for Inria, for CNRS, for CNES, for LIRMM or for Rémi Gribonval using HalTools Jaime Arias [email protected] (CC-BY 4.0) A Hands-On Introduction to Software Heritage November 4, 2025 24 / 25