Is caerp-payment safe to use?

caerp-payment has no known vulnerabilities on the latest version (2024.0.11). DepScope rates its health at 48/100 (high risk).

What is the latest version of caerp-payment?

The latest version of caerp-payment is 2024.0.11, released 2025-11-05.

Does caerp-payment have known vulnerabilities?

No known vulnerabilities on the latest version of caerp-payment.

Is caerp-payment deprecated?

No, caerp-payment is actively maintained. Latest release: 2024.0.11 (2025-11-05).

What are alternatives to caerp-payment?

Popular alternatives to caerp-payment in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does caerp-payment use?

caerp-payment is licensed under GPLv3.

caerp-payment

pypiv2024.0.11

caerp_payment

License GPLv3strong copyleft10 versions1 maintainers3 deps

/ 100

Health

safe to use

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

Health breakdown0 – 100

15/25

maintenance

0/20

popularity

25/25

security

6/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

WebTest pytest;pytest-cov;

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/caerp-payment