Pydantic Logfire
Pydantic Logfire helps you understand what your Python application is doing through traces, logs, and metrics.
pip install logfire
Import Logfire in your application:
import logfire
See the Logfire documentation to get started.
5 maintainers
Metadata
5 maintainers
Release files for logfire 5.6.0
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 |
|---|---|---|---|---|
| logfire-5.6.0.tar.gz | 3.3 kB | With provenance | Details for logfire-5.6.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| logfire-5.6.0-py3-none-any.whl | Python 3 | none | any | Details for logfire-5.6.0-py3-none-any.whl |
Total release size: 6.4 kB
Release files / logfire-5.6.0.tar.gz
| Download URL | logfire-5.6.0.tar.gz |
|---|---|
| Size | 3.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a28f9063eb0110b6c26240aa54e4313ce5953f0512a10d999660401db0ec37d0
|
|
BLAKE2b-256 checksum How to use checksums |
75749924a954e45fc69f1dfeef05307ce8afa22a3a2233cc80fdb0d1c341b61d
|
| 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 11, 2026.
Transparency logRelease files / logfire-5.6.0-py3-none-any.whl
| Download URL | logfire-5.6.0-py3-none-any.whl |
|---|---|
| Size | 3.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b9b874733f097c7526ccdb5f447ce0817cf1743ad2d5c3dc14afc428cdf96788
|
|
BLAKE2b-256 checksum How to use checksums |
0b6c83f37b2d50214deb3410b3e32c31008ca9a10495c93fd07ac123c6ffb0bf
|
| 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 11, 2026.
Transparency logSecurity for logfire 5.6.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.
Attestation for logfire-5.6.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 11, 2026.
Transparency logA 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.
