Skip to main content
  • Home
  • Development
  • Documentation
  • Donate
  • Operational login
  • Browse the archive

swh logo
SoftwareHeritage
Software
Heritage
Archive
Features
  • Search

  • Downloads

  • Save code now

  • Add forge now

  • Help

  • b2dfb87
  • /
  • .gitlab-ci.yml
Raw File Download

To reference or cite the objects present in the Software Heritage archive, permalinks based on SoftWare Hash IDentifiers (SWHIDs) must be used.
Select below a type of object currently browsed in order to display its associated SWHID and permalink.

  • content
  • directory
content badge
swh:1:cnt:36f2647b9fd87e86e387ea5d496dd73234782147
directory badge
swh:1:dir:b2dfb87cdbe2bfa5d9460e748f2b2fe27e189806

This interface enables to generate software citations, provided that the root directory of browsed objects contains a citation.cff or codemeta.json file.
Select below a type of object currently browsed in order to generate citations for them.

  • content
  • directory
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
Generate software citation in BibTex format (requires biblatex-software package)
Generating citation ...
.gitlab-ci.yml
pages:
  artifacts:
    paths:
    - public
  image: sphinxdoc/sphinx
  only:
  - main
  script:
  - apt -yq update
  - apt -yq install git
  - bash ./scripts/build_documentation.sh -i public
  stage: deploy
  tags:
  - ci.inria.fr
  - linux
  - small
release_job:
  image: registry.gitlab.com/gitlab-org/release-cli:latest
  release:
    description: Release $CI_COMMIT_TAG
    tag_name: $CI_COMMIT_TAG
  rules:
  - if: $CI_COMMIT_TAG
  script:
  - echo "running release_job"
  stage: release
  tags:
  - ci.inria.fr
  - linux
  - small
stages:
- release
- deploy

back to top

Software Heritage — Copyright (C) 2015–2026, 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— Content policy— Contact— JavaScript license information— Web API