I will be talking to #opensource #automotive professionals about #swhid at the Automotive Open-Source Governance Monthly Discussions, from OpenChain, on March 26th at 11:00 UTC
https://openchain-project.github.io/Automotive-Open-Source-Governance-Monthly/
What's if you could ~$ git clone SWHID?
"You’d end up with git clone as a content-addressed fetch primitive rather than just a URL fetch, which is an interesting building block for reproducible builds and supply chain verification."
A nice write-up by @andrewnez on git remote helpers 👉 https://nesbitt.io/2026/03/18/git-remote-helpers.html
[...] "I just explained the syntax of SWHID, describing how their core identifier and optional qualifiers combine to uniquely reference software artifacts, as well as specific fragments within them. "
https://toscalix.com/2026/03/17/description-of-swhid-syntax/
#swhid #swidentifier #provenance #traceability #integrity #compliance
This article explains the syntax of #swhid describing how the core identifier and optional qualifiers are structured. It shows how SWHIDs can reference software artifacts such as files, directories, revisions, and releases, and how their design enables precise comparison of software.
What is the best way to identify software? My first article of a series about #swhid
http://toscalix.com/2026/03/10/what-is-the-best-way-to-identify-software-introducing-swhid/
https://www.softwareheritage.org/2026/02/18/swhid-car/ (Why you may want to put a SWHID in your next car)
--<--
In the world of high-stakes automotive engineering, road safety is increasingly a software problem.
For Wendi Urribarri, Process and Safety Engineer at Woven by Toyota, the solution lies in the cryptographic DNA of the car’s codebase.
She argues that the SoftWare Hash Identifier (SWHID) could become a critical safety feature: by providing an immutable, verifiable fingerprint for every component in a vehicle’s massive software stack, SWHIDs ensure that the code running on the road is exactly what was vetted in the lab.
-->--
#SoftwareHeritage #SWHID
This coming Monday Mar 2nd at 17: 00 CET I will be speaking online about Software Hash Identifier, at the CRA Mondays sessions, organised by the @orcwg at the @EclipseFdn
I will describe the relevance of intrinsic identifiers, describe #swhid, provide some use cases and discuss with the audience the relevance of identifiers such SWHID in the context of the Cyber Resilience Act.
#intrinsicidentifier #provenance #compliance #cra #sbom @swheritage
« there are the systemic drivers:
• FAIR data mandates from funders
• Open-lab notebook movements
• Persistent Identifier (PID) expansion into every layer of research
• Preprint-to-publication workflows that treat research as a continuum
All of these point toward a future where the “unit of science” is no longer a PDF but a rich, evolving digital object grounded in data, workflows, and provenance. »
🧐 Guess what?
‣ #Guix and #Nix are designed around Persistent IDentifier (PID) for dealing with reproducible computational environments.
‣ Software Hash IDentifier (#SWHID) proposed by #SoftwareHeritage folk provides a Persistent IDentifier (PID) for source code.
https://scholarlykitchen.sspnet.org/2026/02/05/back-to-the-article-of-the-future-an-interview-with-sami-benchekroun-and-rod-cookson/
#ReproducibleResearch #OpenScience
2/3
In this interview with Alice Meadows, Sami Benchekroun (Morressier/Molecular Connections) and Rod Cookson (The Royal Society) share their thoughts about how and why scholarly publishing needs to move away from being article-based.
"Meet the SWHID: The end of broken links, broken builds"
#SoftwareHeritage #SWH #SWHID #Links #Software ...
https://www.softwareheritage.org/2025/11/20/swhid-seminar-post/
toscalix
Bastien Guerry 🧢
pvergain (kolektiva)
Simon Tournier
gaby_wald
Software Heritage