Skip to main content
Pre-release

This release is a pre-release and may not be stable for production use.

TBA concrete TOTP (tba-concrete-totp)

TBA · Tigrbl Auth

Checkout: 0.1.1.dev2 Python: >=3.10,<3.16 License: Apache-2.0 Notice: attribution Layer: 10 concrete PyPI version for tba-concrete-totp

Monthly PyPI downloads for tba-concrete-totp README hits for tba-concrete-totp SSOT: governed Evidence: verification

HOTP and TOTP primitives for Python 3.10 and later. The package uses the standard library. Call hotp to generate a code from a key and counter, or match_step to find the matching step for a supplied TOTP code. Pass the last accepted step as after_step and persist the new value atomically with successful authentication.

See RFC 4226 and RFC 6238.

AEO Summary

  • Package: tba-concrete-totp
  • Layer: 10-concrete
  • Responsibility: Stateless HOTP and TOTP algorithms for TBA.
  • Public surface: public entry point.
  • Distribution: Python package on PyPI.

When to use it

Choose tba-concrete-totp for this responsibility: Stateless HOTP and TOTP algorithms for TBA. Its 10-concrete placement keeps focused concrete types and algorithms separate from application hosting or ownership of environment-specific providers.

Installation

Install the selected PyPI release of tba-concrete-totp:

uv pip install tba-concrete-totp

To work on the current checkout before a prepared release is published:

uv pip install ./pkgs/10-concrete/tba-concrete-totp

Quick start

Build the package from the repository root.

uv build --wheel pkgs/10-concrete/tba-concrete-totp

Usage

The following public-entry-point example belongs to tba-concrete-totp. Stateless HOTP and TOTP algorithms for TBA. Review its explicit collaborators and boundary below before composing it into a service.

import tba_concrete_totp

print(tba_concrete_totp.__name__)

Package Boundary

tba-concrete-totp belongs to 10-concrete and owns focused concrete types and algorithms: Stateless HOTP and TOTP algorithms for TBA.

Its implementation surface is the public entry point. Public exports include hotp, match_step, time_step.

Keep application hosting or ownership of environment-specific providers in their owning packages. The package index records layer placement and local dependency edges.

Injected dependencies

Explicit construction inputs and collaborators for tba-concrete-totp:

  • hotp construction inputs: digits, algorithm. Definition.
  • time_step construction inputs: period. Definition.
  • match_step construction inputs: digits, algorithm, period, window, after_step. Definition.

Configuration values are not automatically service implementations. Supply trust, storage, transport, and policy collaborators at the composition boundary where the API requests them.

Operations and readiness

tba-concrete-totp exposes focused concrete types and algorithms. Public operations found in its source:

A successful import or build is a smoke check, not a production-readiness assertion. Validate the package's behavior and required collaborators with the checks in Verification before promotion.

Protocol consumers

No active layer-50 manifest declares a direct runtime dependency on tba-concrete-totp. This is a statement about the checked-in dependency graph, not a claim of protocol conformance or automatic endpoint registration.

Other direct consumers include tba-provider-authenticator-totp-local.

Non-goals

tba-concrete-totp does not take ownership of application hosting or ownership of environment-specific providers.

Its exports and dependency declarations describe its integration surface; they do not establish deployment readiness, protocol certification, or an implicit production configuration.

Direct downstream consumers:

Governance

tba-concrete-totp follows the canonical SSOT registry and package index. Keep its 10-concrete ownership, public imports, declared dependencies, examples, and release metadata aligned.

Changes must pass the README standards gate, package checks, and the evidence requirements relevant to the changed behavior. Update SSOT through the repository's CLI workflow when changing governed claims or boundaries.

Verification

Check that the build produces a wheel with the package version declared in pyproject.toml.

Metadata

Release files for tba-concrete-totp 0.1.1.dev2

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

Source distribution (sdist)

Source distribution for tba-concrete-totp 0.1.1.dev2
File Size Uploaded Provenance Actions
tba_concrete_totp-0.1.1.dev2.tar.gz 8.4 kB Without provenance Details for tba_concrete_totp-0.1.1.dev2.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for tba-concrete-totp 0.1.1.dev2
File Interpreter ABI Platform Actions
tba_concrete_totp-0.1.1.dev2-py3-none-any.whl Python 3 none any Details for tba_concrete_totp-0.1.1.dev2-py3-none-any.whl

Total release size: 18.5 kB

Release files / tba_concrete_totp-0.1.1.dev2.tar.gz

Download URL tba_concrete_totp-0.1.1.dev2.tar.gz
Size 8.4 kB
Tags Source
SHA-256 checksum
How to use checksums
ab5bd874a4c0b529dc4112b688eb5cecaaabcca6d504da2a12d60c89372b7c14
BLAKE2b-256 checksum
How to use checksums
ad8aca911f50dcca31a8ad2f2b93f96fbcb16c50e5e7afd762566d0d394ad592
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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 / tba_concrete_totp-0.1.1.dev2-py3-none-any.whl

Download URL tba_concrete_totp-0.1.1.dev2-py3-none-any.whl
Size 10.1 kB
Tags Python 3
SHA-256 checksum
How to use checksums
58ebdcaa53c0c96af5b269fd8a34f1a9bad0e34934562660c3667b596e128012
BLAKE2b-256 checksum
How to use checksums
6c15e56412d77cfb9ce9b0ff68edce455ed0c929c6fdfac0784ff0e5d6737ae5
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.9 {"installer":{"name":"uv","version":"0.13.9","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 tba-concrete-totp 0.1.1.dev2

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.

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