Is call-to-change safe to use?

call-to-change has no known vulnerabilities on the latest version (0.8.7). DepScope rates its health at 0/100 (unknown risk).

What is the latest version of call-to-change?

The latest version of call-to-change is 0.8.7, released 2024-10-19.

Does call-to-change have known vulnerabilities?

No known vulnerabilities on the latest version of call-to-change.

Is call-to-change deprecated?

No, call-to-change is actively maintained. Latest release: 0.8.7 (2024-10-19).

What are alternatives to call-to-change?

Popular alternatives to call-to-change in PyPI include: boto3, packaging, urllib3, idna, certifi.

What license does call-to-change use?

License information for call-to-change is not declared in the registry metadata.

call-to-change

pypiv0.8.7

8 versions2 deps

/ 100

Health

insufficient data

call-to-change has limited data (2/6 signals) — verify manually before use

Limited information available for this package
Moderate health score (36/100) — verify manually

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

openai requests

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/call-to-change