Is logfire-api safe to use?

logfire-api has no known vulnerabilities on the latest version (4.33.0). DepScope rates its health at 82/100 (low risk).

What is the latest version of logfire-api?

The latest version of logfire-api is 4.33.0, released 2026-05-13.

Does logfire-api have known vulnerabilities?

No known vulnerabilities on the latest version of logfire-api.

Is logfire-api deprecated?

No, logfire-api is actively maintained. Latest release: 4.33.0 (2026-05-13).

What are alternatives to logfire-api?

Popular alternatives to logfire-api in PyPI include: boto3, packaging, idna, urllib3, requests.

What license does logfire-api use?

logfire-api is licensed under MIT.

logfire-api

pypiv4.33.0

Shim for the Logfire SDK which does nothing unless Logfire is installed

License MITpermissive135 versions0 deps4,680,162 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 82/100)

Health breakdown0 – 100

25/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

0/15

community

0/15

popularity_floor

Vulnerabilities

none known

Quality signals

Publish security

API token

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/logfire-api

logfire-api

pypiv4.33.0

Shim for the Logfire SDK which does nothing unless Logfire is installed

License MITpermissive135 versions0 deps4,680,162 weekly dl

/ 100

Health

safe to use

[email protected] is safe to use (health: 82/100)

Health breakdown0 – 100

25/25

maintenance

17/20

popularity

25/25

security

15/15

maturity

0/15

community

0/15

popularity_floor

Vulnerabilities

none known

Quality signals

Publish security

API token

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/logfire-api