Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Save code now

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

You can contribute to extend the content of the Software Heritage archive by submitting an origin save request. To do so, fill the required info in the form below:

The origin type must be specified
The origin url is not valid or does not reference a code repository

The archives visit type enables to save multiple source code archive files (*.tar.gz, *.zip) under a same software origin.
For each archive file to save, the source code will then be available inside a branch named releases/<version> from the snapshot generated by Software Heritage.
All archive files previously saved under the software origin will always be available in each snapshot generated by a new visit.
Please use the form below to add such artifacts to save before submitting a request.

swh spinner

Processing "save code now" request ...

  • Help
  • Browse save requests

A "Save code now" request takes the following parameters:

  • Origin type: the type of software origin. Currently, the supported types are:
    • git, for origins using Git
    • hg, for origins using Mercurial
    • svn, for origins using Subversion
    • cvs, for origins using CVS
    • bzr, for origins using Bazaar
    • tarball, for tarball origins
  • Origin URL: the URL of the remote repository for the software origin or the URL for downloading a tarball .
    In order to avoid saving errors from Software Heritage, you should provide the clone/checkout URL as given by the provider hosting the software origin.
    It can easily be found in the web interface used to browse the software origin.
    For instance, if you want to save a git origin into the archive, you should check that the command $ git clone <origin_url>
    does not return an error before submitting a request.

Once submitted, your save request can either be:

  • accepted: a visit to the provided origin will then be scheduled by Software Heritage in order to load its content into the archive as soon as possible
  • rejected: the provided origin URL is blacklisted and no visit will be scheduled
  • put in pending state: a manual review will then be performed in order to determine if the origin can be safely loaded or not into the archive

Once a save request has been accepted, you can follow its current status in the submitted save requests list.
If you submitted requests while authenticated, you will be able to only display your own requests.

Software Heritage — Copyright (C) 2015–2025, The Software Heritage developers. License: GNU AGPLv3+.
The source code of Software Heritage itself is available on our development forge.
The source code files archived by Software Heritage are available under their own copyright and licenses.
Terms of use: Archive access, API— Contact— JavaScript license information— Web API

back to top