Skip to main content

repoproviders

Package Latest PyPI Version Supported Python Versions Documentation
Meta BSD-3-Clause Code of Conduct Checked with mypy Code Style Black
Automation

Detect, resolve and fetch repositories of content

Supported Repositories

Repository Resolver Fetcher
GitHub Repos ✅ ✅
GitHub Refs (Commits, Tags, Branches) ✅ ✅
GitHub PRs ✅ ✅
GitHub Action Artifacts ✅ ✅
Gists ✅ ✅
Git Repos ✅ ✅
GitLab Repos ✅ ✅
GitLab Refs (Commits, Tags, Branches) ✅ ✅
Google Drive Folders (Public) ✅ ✅
DOI ✅ N/A
Zenodo Repositories ✅ ✅
Dataverse Repositories ✅ ✅
Figshare ✅ ✅
Hydroshare ✅ ✅
Mercurial ❌ ❌
CKAN ❌ ❌
Software Heritage ❌ ❌
ZIP files over HTTP ❌ ❌
Codeberg Refs ❌ ❌

Examples

You can try these out with a pip install repoproviders.

# Resolve a GitHub reference
➜ repoproviders resolve https://github.com/yuvipanda/requirements
Git(repo='https://github.com/yuvipanda/requirements', ref='HEAD')
ImmutableGit(repo='https://github.com/yuvipanda/requirements', ref='5a8737831f74a97bf71a7c4e1500fa0223b13d0d')

# Resolve a GitHub reference to a specific branch based on a URL
➜ repoproviders resolve https://github.com/yuvipanda/requirements/tree/master
Git(repo='https://github.com/yuvipanda/requirements', ref='master')
ImmutableGit(repo='https://github.com/yuvipanda/requirements', ref='5a8737831f74a97bf71a7c4e1500fa0223b13d0d')

# Resolve a DOI
➜ repoproviders resolve 10.1126/science.aar3646
Doi(url='https://www.science.org/doi/10.1126/science.aar3646')

# Resolve a DOI that points to another resolver we support (Dataverse)
➜ repoproviders resolve 10.7910/DVN/6ZXAGT
Doi(url='https://dataverse.harvard.edu/citation?persistentId=doi:10.7910/DVN/6ZXAGT')
DataverseDataset(installationUrl='https://dataverse.harvard.edu', persistentId='doi:10.7910/DVN/6ZXAGT')```

# Resolve a Zenodo DOI
➜ repoproviders resolve 10.5281/zenodo.805993
Doi(url='https://zenodo.org/doi/10.5281/zenodo.805993')
ZenodoDataset(installationUrl='https://zenodo.org/', recordId='14007206')

# Resolve a Zenodo URL directly
➜ repoproviders resolve https://zenodo.org/records/14007206
ZenodoDataset(installationUrl='https://zenodo.org/', recordId='14007206')

Copyright

Metadata

Release files for repoproviders 0.1.10

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for repoproviders 0.1.10
File Size Uploaded
repoproviders-0.1.10.tar.gz 59.1 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for repoproviders 0.1.10
File Interpreter ABI Platform
repoproviders-0.1.10-py2.py3-none-any.whl Python 2, Python 3 none any Details

Total release size: 111.9 kB

Release files / repoproviders-0.1.10.tar.gz

Download URL repoproviders-0.1.10.tar.gz
Size 59.1 kB
Tags Source
SHA-256 checksum
How to use checksums
ef93729af7a3a59cbcee323a18c2efe5cbaf88901488848c2159824c9a8fe3c7
BLAKE2b-256 checksum
How to use checksums
598b920591e3b4cf5651e43d939045b6c40e335c75191bfd4bb77d6d497742c0
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.

Transparency log

Release files / repoproviders-0.1.10-py2.py3-none-any.whl

Download URL repoproviders-0.1.10-py2.py3-none-any.whl
Size 52.8 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
cfa0fedced9b3da17ec26abece37686f29dfe2a74f414cd90bf37bf4425c8e1c
BLAKE2b-256 checksum
How to use checksums
dbf9043de1083e0b1c78ca981f16f4aaf4551be1384c5c85590de501a7ff9072
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.13.7

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Feb 13, 2026.

Transparency log

Release history Release notifications | RSS feed

This release

0.1.10 This release

2 release files

0.1.9

2 release files

0.1.8

2 release files

0.1.7

2 release files

0.1.6

2 release files

0.1.5

2 release files

0.1.4

2 release files

0.1.3

2 release files

0.1.2

2 release files

0.1.1

2 release files

0.1.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page