Software Heritage is a nonprofit initiative that collects, preserves, and makes source code available through a universal archive, using persistent identifiers and graph-based provenance. It addresses preservation of publicly obtainable code rather than operation of safety-critical systems.
No partnership implied. Relationship: indexed only; no formal relationship. substantive editorial profile; independent review pending
Stable ID
entity-software-heritage
Entity kind
nonprofit universal source-code archive
Category
University and national laboratory
Geography
France / international
Editorial reviewer
GShips Project editorial synthesis
Official link checked
2026-07-25
Profile boundary
Software Heritage is a nonprofit initiative that collects, preserves, and makes source code available through a universal archive, using persistent identifiers and graph-based provenance. It addresses preservation of publicly obtainable code rather than operation of safety-critical systems.
Evidence boundary: Official-link review: the site was reachable and documents the archive mission, identifiers, data model, and access services. Preservation guarantees, service levels, legal coverage, future funding, and suitability for centuries were not independently verified; independent review pending.
Potentially relevant capability areas
Source-code collection and preservation, provenance graphs, persistent identifiers, archival APIs, and scholarly software infrastructure.
Task-specific matches
A match is bounded to one declared work program. It does not establish a partnership, availability, endorsement, or an organization-wide rank.
No task-specific match is recorded.
Potential fit—not a relationship
Could inform durable software provenance, archival identifiers, dependency evidence, and recovery copies for an open technology commons, especially when paired with reproducible builds and offline archives.
Possible bounded engagement, not undertaken: Proposed only, subject to a future fit check and repository policies: archive eligible public GShips code through normal mechanisms and evaluate offline export and independent mirrors before any deeper institutional inquiry. No outreach, special deposit, commitment, or procurement has occurred.
Fit and engagement risks
Archival presence does not prove build reproducibility, security, correctness, licensing clarity, or long-term executability.
Repository ingestion and API availability can change, and private or restricted code may not be eligible.
A single institutional archive is insufficient for multigenerational preservation without geographic and media diversity.
What would change this profile?
Verified archive ingestion, reproducible recovery drills, documented offline snapshots, multiple independent mirrors, and clear licensing would strengthen the preservation case.
Official-link review: the site was reachable and documents the archive mission, identifiers, data model, and access services. Preservation guarantees, service levels, legal coverage, future funding, and suitability for centuries were not independently verified; independent review pending.
Potential fit is an editorial hypothesis. Inclusion does not establish affiliation, endorsement, procurement eligibility, or a relationship.
What would change this page?
Verified archive ingestion, reproducible recovery drills, documented offline snapshots, multiple independent mirrors, and clear licensing would strengthen the preservation case.
Conflicts were not assessed beyond publisher disclosure in this official-link review; sponsors, hosting institutions, repository relationships, and licensing conflicts were not independently investigated.
The maintainer intends to explore a commercial venture based on some GShips work. No entity, outside funding, customer, sponsor, or indexed-organization relationship currently exists.