All integrationsCode Repositories
Software Heritage
Search the Software Heritage archive of public source code: look up a repository and its visits, branches, commits, releases, folders and files, resolve SWHIDs, get citations, metadata and known vulnerabilities, ask for a repository to be archived, and run a workflow when the archive visits one.
- actions
- 19
- trigger
- 1
Triggers
Start a workflow when something happens in Software Heritage.
- New archive visitTriggers once for each visit Software Heritage finishes to a repository, with the snapshot of branches and tags it took, optionally only visits of one type or only those that found changes. Visits finished before you turn it on never trigger it. It checks every 30 minutes.
Actions
Steps a workflow can run in Software Heritage.
- Search repositoriesFind repositories in the archive whose address contains some text, e.g. a project or owner name, with how often and when the archive last visited each. Returns a page at a time.
- Get repositoryCheck that a repository is in the archive and get the address it is filed under, its SWHID, how the archive reads it and its page.
- List visitsList the times the archive read a repository, newest first: when, how it went, and the snapshot of branches and tags it took.
- Get visitGet one visit of a repository, the latest unless you give its number: when it was, how it went and the snapshot it took.
- List branchesList the branches and tags in a snapshot, or in a repository's latest one, with the commit or release each points at. HEAD shows the default branch's latest commit.
- Get commitGet an archived commit: its message, author, committer, dates, the commits before it and its top folder.
- List commit historyList the commits leading to a commit, starting with it and going back in time, like git log.
- Get releaseGet an archived release (a tag): its name, message, author, date and the commit it marks.
- List folderList the files and folders in an archived folder, or in a commit's files at a path, with each one's size and SWHID. A path to a file gives that one file.
- Get fileCheck an archived file and get its size, its SWHID and its SHA1, SHA256 and other checksums.
- Get file textRead an archived text file, such as a README or source file, up to a number of bytes. Binary files are refused.
- Resolve SWHIDCheck that a SWHID names something in the archive and get what it is, its repository, path and lines when it says, and its page.
- Check SWHIDs are archivedCheck which of up to 1,000 SWHIDs of files, folders, commits, releases or snapshots are in the archive.
- Get archive statisticsGet how many repositories, visits, files, folders, commits, releases and authors the archive holds.
- Get citationGet a citation for software in BibTeX or CSL JSON, made from its codemeta.json or CITATION.cff in the archive, with its SWHID.
- Get software metadataGet what a repository says about itself, read from files such as codemeta.json and package.json: name, description, version, licences, authors, languages and keywords.
- List vulnerabilitiesList the known security vulnerabilities, such as CVEs, that affect a commit, with their severity, references and fixing commits, from the osv.dev database.
- Request an archive of a repositoryAsk Software Heritage to archive a public repository now (its Save Code Now). Well known forges such as GitHub are accepted at once; other addresses wait for a check.
- Get save request statusCheck how a request to archive a repository is going, by its number, or list a repository's requests, newest first.
No actions match that.
Automate Software Heritage with Lodol.
Connect Software Heritage and ask your AI for your first workflow.
Free plan, no credit card