# Tea articles

## Pages

- [Announcing sbomify v26.2.0: The One That Signs the DoC](https://sbomify.com/2026/05/13/announcing-sbomify-v26-2-0-the-one-that-signs-the-doc/) (2026-05-13): sbomify v26.2.0 completes the EU CRA workflow with a signed Declaration of Conformity, adds Component Lifecycle Events, SBOM signatures and provenance, and full CycloneDX 1.7 / SPDX 3.0.1 support.
- [Announcing sbomify v26.1.0: The One Where We Switch to CalVer](https://sbomify.com/2026/04/02/announcing-sbomify-v26-1-0-the-one-where-we-switch-to-calver/) (2026-04-02): sbomify v26.1.0 introduces the CRA Compliance Wizard, switches to CalVer versioning, adds Trust Center subdomain routing, and brings full TEA v0.4.0 compatibility.
- [SBOM Adoption on PyPI Is at 1.58%. We Can Do Better.](https://sbomify.com/2026/03/12/pypi-sbom-analysis/) (2026-03-12): We scanned 15,021 of the most popular Python packages for PEP 770 SBOMs. Only 1.58% include one, and every single SBOM is CycloneDX. Here are the full results.
- [Why We're Bullish on TEA, And Why You Should Be Too](https://sbomify.com/2026/03/01/why-were-bullish-on-tea/) (2026-03-01): The Transparency Exchange API (TEA) is the missing standard for automated SBOM discovery and exchange. Here's what it is, why it matters, and why sbomify is all in.
- [Announcing sbomify v0.27: The One with TEA](https://sbomify.com/2026/02/24/announcing-sbomify-v0-27-the-one-with-tea/) (2026-02-24): sbomify v0.27 adds full Transparency Exchange API (TEA) support, SPDX 3.0 compatibility, scoped access tokens, and improved account management.

---

From sbomify: https://sbomify.com/tags/tea/
