Is burning-cost safe to use?

burning-cost has no known vulnerabilities on the latest version (0.1.0). DepScope rates its health at 54/100 (high risk).

What is the latest version of burning-cost?

The latest version of burning-cost is 0.1.0, released 2026-03-23.

No known vulnerabilities on the latest version of burning-cost.

No, burning-cost is actively maintained. Latest release: 0.1.0 (2026-03-23).

Popular alternatives to burning-cost in PyPI include: boto3, packaging, urllib3, idna, typing-extensions.

burning-cost is licensed under MIT.

pypiv0.1.0

Meta-package installing the full Burning Cost insurance pricing toolkit

License MITpermissive1 versions10 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Dependencies (10)

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/burning-cost