tigrbl_auth
Tigrbl-native authentication and authorization package for the Tigrbl ecosystem.
Repository state
This checkpoint is a Step 12 final certification aggregation checkpoint with follow-up target/profile truth reconciliation and clean-room executor / validated-evidence contract hardening layered on top of the earlier certification-target, clean-room-matrix, published-dependency, runtime-validation, test-graph, production-grade operator-control-plane, migration-portability, fail-closed-gates, and Tier 4 peer-program work.
The current repository truth is:
fully_certifiable_now = falsefully_rfc_compliant_now = falsestrict_independent_claims_ready = falseprofile_scope_mismatch_set_empty = truealignment_only_checkpoint_no_new_certification_evidence = falseclean_room_executor_matrix_declared_complete = truevalidated_manifest_identity_contract_installed = true- the package is not yet certifiably fully featured
- the package is not yet certifiably fully RFC/spec compliant
Final package-level certification is still blocked because the fail-closed validated execution gates remain incomplete for the clean-room runtime matrix, in-scope certification lanes, migration portability preservation, Tier 3 evidence rebuilt from validated runs, and preserved Tier 4 external peer bundles.
This update keeps the retained target/profile mismatch set empty for RFC 7516, RFC 7592, and RFC 9207, and it also hardens the preserved evidence model so runtime, test-lane, and migration manifests only count as passing when they carry identity, install-substrate linkage, environment identity, and the expected runtime / pytest / revision-aware backend artifacts.
Start with:
docs/compliance/AUTHORITATIVE_CURRENT_DOCS.mdCURRENT_STATE.mdCERTIFICATION_STATUS.mddocs/compliance/current_state_report.mddocs/compliance/certification_state_report.mddocs/compliance/release_gate_report.mddocs/compliance/runtime_profile_report.mddocs/compliance/validated_execution_report.mddocs/compliance/PEER_MATRIX_REPORT.mddocs/compliance/TIER4_PROMOTION_MATRIX.mddocs/compliance/RELEASE_DECISION_RECORD.mddocs/compliance/CLEAN_ROOM_EXECUTOR_AND_EVIDENCE_CHECKPOINT_2026-03-27.md
Historical planning and scaffold-layout documents are retained under docs/archive/ and are non-authoritative for the current repository state.
Runtime entrypoints
- standalone gateway/application export:
tigrbl_auth.gateway:app - application factory export:
tigrbl_auth.app:app - plugin installation:
tigrbl_auth.plugin:TigrblAuthPlugin
Current runtime model
The package is treated as an ASGI 3 application package, not as a single bundled server. Runtime-serving claims are separated into runner profiles. Uvicorn, Hypercorn, and Tigrcorn are declared as runner-qualified certification targets, and the serve operator can launch runtime when the selected runner profile is installed and the Tigrbl runtime stack is importable in the active environment.
Tigrbl-only policy
This checkpoint remains intentionally aligned to Tigrbl guidance:
- prefer Tigrbl exports and Tigrbl type exports,
- use Tigrbl ops and surfaces rather than ad-hoc framework routes,
- avoid direct FastAPI or Starlette imports and dependencies in verified release scopes.
Installation profiles
Base install
pip install -c constraints/base.txt .
Storage extras
pip install -c constraints/base.txt '.[postgres]'
pip install -c constraints/base.txt '.[sqlite]'
Runner extras
pip install -c constraints/base.txt -c constraints/runner-uvicorn.txt '.[uvicorn]'
pip install -c constraints/base.txt -c constraints/runner-hypercorn.txt '.[hypercorn]'
pip install -c constraints/base.txt -c constraints/runner-tigrcorn.txt '.[tigrcorn]'
pip install -c constraints/base.txt -c constraints/runner-uvicorn.txt -c constraints/runner-hypercorn.txt -c constraints/runner-tigrcorn.txt '.[servers]'
The tigrcorn extra is pinned to a published Tigrcorn runner package for Python 3.11 and 3.12. Final certification is still blocked until preserved clean-room execution evidence exists for the full supported runtime/test/migration matrix and the Tier 4 external peer bundles are complete.
Run
tigrbl-auth claims lint
or embed as a plugin:
from tigrbl import TigrblApp
from tigrbl_auth.plugin import TigrblAuthPlugin
app = TigrblApp()
plugin = TigrblAuthPlugin()
plugin.install(app)
Notes
- OAuth 2.1 alignment is tracked as a profile, not as a formal RFC claim.
keysis the canonical certified command family;keyis no longer part of the certified operator surface.- public "independent" wording remains disallowed until preserved Tier 4 external peer bundles exist and promote the retained boundary.
- The authoritative executable CLI surface is
tigrbl_auth/cli/metadata.pyplus the generateddocs/reference/CLI_SURFACE.md. - A current checkpoint gap review remains published at
docs/compliance/PACKAGE_REVIEW_GAP_ANALYSIS.md. - Supplemental supporting review/plan docs remain available at
docs/compliance/INDEPENDENT_PACKAGE_REVIEW_2026-03-27.mdanddocs/compliance/CERTIFIABLE_DELIVERY_PLAN_2026-03-27.md; the current authoritative truth is in the generated reports and top-level current-state docs. - Dependency provenance for this checkpoint is preserved in
pyproject.toml,constraints/*.txt, andconstraints/dependency-lock.json.
Known current blockers
- preserved Tier 4 external peer bundles are still absent and
strict_independent_claims_readyremainsfalse - the package is still not truthfully certifiably fully featured or fully RFC/spec compliant because the fail-closed validated execution gates remain red
- validated clean-room runtime matrix evidence is not yet fully preserved as passing
- validated in-scope certification lane evidence is not yet fully preserved as passing
- SQLite and PostgreSQL migration portability has not yet been preserved as passing in the final validated execution report
- Tier 3 evidence has not yet been explicitly rebuilt from validated-run manifests in a fully green final gate set
- the supported interpreter range remains Python
3.10–3.12; this local checkpoint container only provides Python3.13, so it cannot truthfully generate the required preserved supported-matrix evidence by itself - release bundles and attestation verification can be rebuilt from this checkpoint, but the result remains a final-release candidate, not a truthful final certification release
License
Apache-2.0
Clean-room certification matrix
Use tox.ini for the same profile commands locally and in CI.
Examples:
tox -e py310-basetox -e py311-sqlite-uvicorntox -e py312-postgres-hypercorntox -e py311-tigrcorntox -e py312-devtesttox -e py311-gates
The Tier 4 peer-execution handoff package for the full supported peer-profile set is emitted under dist/tier4-external-handoff/, but preserved independent external bundles are still absent in this checkpoint, so strict independent public claims remain blocked.
Metadata
Release files for tigrbl-auth 0.3.4
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 |
|---|---|---|---|---|
| tigrbl_auth-0.3.4.tar.gz | 306.1 kB | Without provenance | Details for tigrbl_auth-0.3.4.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tigrbl_auth-0.3.4-py3-none-any.whl | Python 3 | none | any | Details for tigrbl_auth-0.3.4-py3-none-any.whl |
Total release size: 743.7 kB
Release files / tigrbl_auth-0.3.4.tar.gz
| Download URL | tigrbl_auth-0.3.4.tar.gz |
|---|---|
| Size | 306.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
91fd7f8b2149d72f5e32220dcad165cbc030ec43cb255230e8b9e62287ea0083
|
|
BLAKE2b-256 checksum How to use checksums |
d08912993e71e91bf17f5b1f7c27ccdb996b8631c729423222888744f2c8d239
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Release files / tigrbl_auth-0.3.4-py3-none-any.whl
| Download URL | tigrbl_auth-0.3.4-py3-none-any.whl |
|---|---|
| Size | 437.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
297c4667af5b400c614c337394c336bbda330b444b8b9ef1838990f59aa0e9a7
|
|
BLAKE2b-256 checksum How to use checksums |
76f5f9f04c17bceb7802dc629aeaba6936ea47757ca77bf548b6592e9d34c67d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.11.2 {"installer":{"name":"uv","version":"0.11.2","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}
|
Security for tigrbl-auth 0.3.4
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.