GitHub Python connector
dex-connector-github implements the six GitHub Query operations declared in
connector.yaml: getAuthenticatedProfile,
listPublicRepositories, listMergedPullRequests, listPullRequestFiles,
listReleases, and listCommits. Its Python release is v0.1.0; the Go release
version remains independent.
The generated project connection resolves credentials at call time and uses the
manifest-driven OAuth refresh driver. It requests read:user, user:email, and
offline_access during authorization. The provider responses must advertise
exactly read:user and user:email in X-OAuth-Scopes; broader scopes select
insufficientScope. The package never stores tokens in Flow input, Attributes,
Results, receipts, or logs.
The profile example is the runnable consuming
application. Its Worker entrypoint is examples/profile/main.py; the Flow
source is examples/profile/flow.py. The real Dex integration test runs that
Flow with an inert local provider stand-in. Provider replay tests use the
Go-recorded scenarios in conformance/connectors/github.
From this directory, run uv sync and uv run pytest -q tests. With a local
Dex stack running, set DEX_FLOW_SERVICE_ADDRESS to its gRPC address and run
uv run pytest -q examples/profile/integration_test.py. The local integration
test does not authorize against GitHub.com. Use Dex Web Connections and the
GitHub OAuth App guide in the manifest for live provider authorization.
Metadata
Release files for dex-connector-github 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| dex_connector_github-0.1.0.tar.gz | 96.4 kB | Without provenance | Details for dex_connector_github-0.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| dex_connector_github-0.1.0-py3-none-any.whl | Python 3 | none | any | Details for dex_connector_github-0.1.0-py3-none-any.whl |
Total release size: 132.9 kB
Release files / dex_connector_github-0.1.0.tar.gz
| Download URL | dex_connector_github-0.1.0.tar.gz |
|---|---|
| Size | 96.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
d4aaf12b3f6d52116c6ec55a19d65a8bf306107e9825d65d4351ce439d38c6fd
|
|
BLAKE2b-256 checksum How to use checksums |
703dc16b1e80e430e9b70d0a78f059f2b018f1eafc8e0f3fb83bfd3c6f6ae7f0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / dex_connector_github-0.1.0-py3-none-any.whl
| Download URL | dex_connector_github-0.1.0-py3-none-any.whl |
|---|---|
| Size | 36.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
40385ab12e4f9de1c5e5018050ebe80f86ec0c8155f98bb4f24e2dd754b20d03
|
|
BLAKE2b-256 checksum How to use checksums |
e4b2addb46aab95e2092d63077f292451c5ac3e4a8516082cc0931741536bb20
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.13.7 {"installer":{"name":"uv","version":"0.13.7","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"26.04","id":"resolute","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for dex-connector-github 0.1.0
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.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.