Is pretty-bad-protocol safe to use?

pretty-bad-protocol has no known vulnerabilities on the latest version (3.1.1). DepScope rates its health at 36/100 (critical risk).

What is the latest version of pretty-bad-protocol?

The latest version of pretty-bad-protocol is 3.1.1, released 2018-08-01.

Does pretty-bad-protocol have known vulnerabilities?

No known vulnerabilities on the latest version of pretty-bad-protocol.

Is pretty-bad-protocol deprecated?

No, pretty-bad-protocol is actively maintained. Latest release: 3.1.1 (2018-08-01).

What are alternatives to pretty-bad-protocol?

Popular alternatives to pretty-bad-protocol in PyPI include: boto3, packaging, certifi, urllib3, idna.

What license does pretty-bad-protocol use?

pretty-bad-protocol is licensed under GPLv3+.

pretty-bad-protocol

pypiv3.1.1

A Python wrapper for GnuPG

License GPLv3+4 versions1 maintainers0 deps5,873 weekly dl

isislovecruft/python-gnupg

/ 100

Health

use with caution

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

Moderate health score (36/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

6/20

popularity

25/25

security

3/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/pretty-bad-protocol