Skip to main content

artifacts-keyring-nofuss

CI

⚠️ This is an unsupported Microsoft sample. Unlike artifacts-keyring, this project is a best-effort alternative focused on convenience (more auth auto-detection, reuse of existing az CLI logins) and debuggability (pure Python — no opaque .NET binary). It is not covered by any Microsoft support program — use at your own risk.

Minimal, pure-Python keyring backend for Azure DevOps Artifacts feeds. Replaces the official artifacts-keyring (which wraps a ~100 MB .NET binary) with a no-fuss, pure-Python implementation — no .NET required.

📖 Documentation

Full docs: https://microsoft.github.io/artifacts-keyring-nofuss/

Page What's inside
Home Install and a scenario picker.
Local development Install packages locally with an az login.
pip & uv setup Turn on the keyring provider once.
GitHub Actions OIDC installs and the Docker composite action.
Docker builds BuildKit secrets and minting a token without az.
GitHub Codespaces The artifacts-helper devcontainer feature.
Managed identity & service principals MI, service principals, and workload identity.
Pre-minted tokens Supply a bearer token via env var or file.
How it works Auth flows, priority order, security model.
Reference Install options, CLI, env vars, feed URLs, troubleshooting.

Quickstart

Install keyring plus this backend as an isolated standalone tool:

uv tool install keyring --with artifacts-keyring-nofuss

Then point your package manager at your private feed — the backend discovers the tenant and obtains credentials automatically:

# pip
pip install --keyring-provider=subprocess \
    --index-url https://pkgs.dev.azure.com/{org}/_packaging/{feed}/pypi/simple/ \
    my-package

# uv
uv pip install my-package \
    --index-url https://__token__@pkgs.dev.azure.com/{org}/_packaging/{feed}/pypi/simple/

See the documentation site for CI, Docker, service principal, and Codespaces setups.

Development

pip install -e ".[dev]"

License

Licensed under the MIT License.

Security

See SECURITY.md for how to report security issues.

Metadata

Release files for artifacts-keyring-nofuss 1.4.0

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

Source distribution (sdist)

Source distribution for artifacts-keyring-nofuss 1.4.0
File Size Uploaded Provenance Actions
artifacts_keyring_nofuss-1.4.0.tar.gz 60.2 kB With provenance Details for artifacts_keyring_nofuss-1.4.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for artifacts-keyring-nofuss 1.4.0
File Interpreter ABI Platform Actions
artifacts_keyring_nofuss-1.4.0-py3-none-any.whl Python 3 none any Details for artifacts_keyring_nofuss-1.4.0-py3-none-any.whl

Total release size: 97.4 kB

Release files / artifacts_keyring_nofuss-1.4.0.tar.gz

Download URL artifacts_keyring_nofuss-1.4.0.tar.gz
Size 60.2 kB
Tags Source
SHA-256 checksum
How to use checksums
02e9e9cae357820e729407cc750d44cd90673ac5e6751c5c9a8e54313fcc8501
BLAKE2b-256 checksum
How to use checksums
e2911f0bfc4b1c1e44819206f686d556d9e8bd04b1bbdeeb001707c54e91d753
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Nov 9, 2026.

Transparency log

Release files / artifacts_keyring_nofuss-1.4.0-py3-none-any.whl

Download URL artifacts_keyring_nofuss-1.4.0-py3-none-any.whl
Size 37.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
5dfc0a06da5432869727f448a6a36490f54803adcf7580f5ab4f68dc7b16c4ba
BLAKE2b-256 checksum
How to use checksums
d7b309386dffb5447c5553df77759970e0ed4955791b384307eb7299f64a2278
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.14

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 Nov 9, 2026.

Transparency log

Security for artifacts-keyring-nofuss 1.4.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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for artifacts_keyring_nofuss-1.4.0.tar.gz

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 Nov 9, 2026.

Transparency log

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.

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