Is dbl-tempo safe to use?

dbl-tempo has no known vulnerabilities on the latest version (0.1.30). DepScope rates its health at 49/100 (high risk).

What is the latest version of dbl-tempo?

The latest version of dbl-tempo is 0.1.30, released 2025-09-15.

Does dbl-tempo have known vulnerabilities?

No known vulnerabilities on the latest version of dbl-tempo.

Is dbl-tempo deprecated?

No, dbl-tempo is actively maintained. Latest release: 0.1.30 (2025-09-15).

What are alternatives to dbl-tempo?

Popular alternatives to dbl-tempo in PyPI include: boto3, packaging, idna, certifi, urllib3.

What license does dbl-tempo use?

dbl-tempo is licensed under MIT.

dbl-tempo

pypiv0.1.30

Tempo is timeseries manipulation for Spark. This project builds upon the capabilities of PySpark to provide a suite of abstractions and functions that make operations on timeseries data easier and highly scalable.

License MITpermissive30 versions1 maintainers0 deps

databrickslabs/tempo

/ 100

Health

use with caution

[email protected] low health (49/100) — consider alternatives

Moderate health score (49/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

0/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/dbl-tempo