This release is a pre-release and may not be stable for production use.
tba-profile-communications-identity-bimi
Optional BIMI Mark Certificate and DNS readiness profile.
Install from the TBA workspace with uv sync --extra bimi.
check_readinessinspects the selected BIMI TXT record and the sender and organizational domains' DMARC enforcement. It returns separate DNS and DMARC findings, the assertion owner after any fallback, and the published asset URLs.readydescribes DNS/DMARC preflight for a mark-backed deployment.verify_certificatetakes a leaf-first PEM bundle and the assertion owner. It checks the certificate policy, classifies CMC/VMC from the signed mark type, matches the assertion domain or selector-qualified SAN, and checks the embedded compressed logotype and its digest. The injected validator checks the certificate path, revocation evidence, and CT evidence.
The readiness policy uses bounded RFC 9989 discovery by default and accepts a
known organizational domain for deployments that need to reproduce a specific
boundary. It checks the legacy pct tag and the current t testing tag.
The lookup is domain-level and does not process message-local selectors or
SPF/DKIM alignment. The embedded-logo check covers format markers and basic
safety checks. Full SVG schema validation, remote asset retrieval, and mailbox
display are separate checks.
Run the example
scripts/bimi_check.py composes the profile with the live TXT resolver or
with TBA's existing ProfiledTrustAnchorProvider and the Mark Certificate
backend. Use the assertion.name returned by the DNS check for the certificate
check. Pass locally obtained evidence and trust material.
uv run --extra bimi python scripts/bimi_check.py dns news.example.com --selector default
uv run --extra bimi python scripts/bimi_check.py verify default._bimi.example.com mark-chain.pem --root mva-root.pem --ct-log ct-log.pem --crl http://ca.example/leaf.crl=leaf.crl --crl http://ca.example/issuer.crl=issuer.crl
In a TBA tenant-admin application, authorize the caller for the sending domain
first. The workspace bimi extra includes the optional workflow adapter.
It composes the profile with the shared communications identity assessment
and TBA's existing durable audit writer. The evidence callback can look up a
local bundle keyed by the discovered assertion owner.
from tba_capability_communications_identity import assess_domain_onboarding, recheck_domain
from tba_durability_audit.operations.audit import append_audit_event_async
from tba_profile_communications_identity_bimi import BimiProfile
from tba_profile_communications_identity_bimi.capability_adapter import BimiDomainChecker
from tba_provider_dns_txt import DnsTxtResolver
bimi = BimiProfile(dns=DnsTxtResolver(), validator=validator)
checker = BimiDomainChecker(bimi, evidence=lambda assertion: bundles.get(assertion.name))
initial = await assess_domain_onboarding(
sending_domain, checker=checker, audit=append_audit_event_async,
db=db, tenant_id=tenant_id,
)
latest = await recheck_domain(
sending_domain, checker=checker, audit=append_audit_event_async,
db=db, tenant_id=tenant_id,
)
References include the BIMI draft, the Mark Certificate verification draft, the v1.8 Mark Certificate requirements, and DMARC RFC 9989.
Quick start
Build the package from the repository root.
uv build --wheel pkgs/55-profiles/tba-profile-communications-identity-bimi
Verification
Check that the build produces a wheel with the package version declared in pyproject.toml.
Metadata
Release files for tba-profile-communications-identity-bimi 0.4.0.dev2
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 |
|---|---|---|---|---|
| tba_profile_communications_identity_bimi-0.4.0.dev2.tar.gz | 8.6 kB | Without provenance | Details for tba_profile_communications_identity_bimi-0.4.0.dev2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| tba_profile_communications_identity_bimi-0.4.0.dev2-py3-none-any.whl | Python 3 | none | any | Details for tba_profile_communications_identity_bimi-0.4.0.dev2-py3-none-any.whl |
Total release size: 18.4 kB
Release files / tba_profile_communications_identity_bimi-0.4.0.dev2.tar.gz
| Download URL | tba_profile_communications_identity_bimi-0.4.0.dev2.tar.gz |
|---|---|
| Size | 8.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
b5975bf18ec5e8a91b256c617182fc318a108a24fead6ffdf976b746ed667aa9
|
|
BLAKE2b-256 checksum How to use checksums |
156c7ab78c10f7b0eaa4a86187c893790b8ee56ddc8a5d654a1216ec067908b3
|
| 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_profile_communications_identity_bimi-0.4.0.dev2-py3-none-any.whl
| Download URL | tba_profile_communications_identity_bimi-0.4.0.dev2-py3-none-any.whl |
|---|---|
| Size | 9.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
86514782bd28e5e8755fb43526327588e6fe9b4f5256a0c264fc1ccfc9af34f1
|
|
BLAKE2b-256 checksum How to use checksums |
e1bcf6136a302def09de094f96bfa320e32ce2215fb589163aa1e071dbfa5153
|
| 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-profile-communications-identity-bimi 0.4.0.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.