Is pep8-naming safe to use?

pep8-naming has no known vulnerabilities on the latest version (0.15.1). DepScope rates its health at 63/100 (moderate risk).

What is the latest version of pep8-naming?

The latest version of pep8-naming is 0.15.1, released 2025-05-05.

Does pep8-naming have known vulnerabilities?

No known vulnerabilities on the latest version of pep8-naming.

Is pep8-naming deprecated?

No, pep8-naming is actively maintained. Latest release: 0.15.1 (2025-05-05).

What are alternatives to pep8-naming?

Popular alternatives to pep8-naming in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does pep8-naming use?

pep8-naming is licensed under Expat license.

pep8-naming

pypiv0.15.1

Check PEP-8 naming conventions, plugin for flake8

License Expat license31 versions1 maintainers1 deps603,440 weekly dl

PyCQA/pep8-naming

/ 100

Health

use with caution

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

Moderate health score (63/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

12/15

maturity

2/15

community

Vulnerabilities

none known

Quality signals

Publish security

API token

Health History

Dependency Tree

License Audit

Dependencies (1)

flake8

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/pep8-naming