Is asymmetric-jwt-auth safe to use?

asymmetric-jwt-auth has no known vulnerabilities on the latest version (1.2.1). DepScope rates its health at 53/100 (high risk).

What is the latest version of asymmetric-jwt-auth?

The latest version of asymmetric-jwt-auth is 1.2.1, released 2025-08-11.

Does asymmetric-jwt-auth have known vulnerabilities?

No known vulnerabilities on the latest version of asymmetric-jwt-auth.

Is asymmetric-jwt-auth deprecated?

No, asymmetric-jwt-auth is actively maintained. Latest release: 1.2.1 (2025-08-11).

What are alternatives to asymmetric-jwt-auth?

Popular alternatives to asymmetric-jwt-auth in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does asymmetric-jwt-auth use?

asymmetric-jwt-auth is licensed under ISC.

asymmetric-jwt-auth

pypiv1.2.1

Asymmetric key based authentication for HTTP APIs

License ISCpermissive36 versions3 deps1,620 weekly dl

https://gitlab.com/thelabnyc/asymmetric-jwt-auth

/ 100

Health

use with caution

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

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

10/25

maintenance

6/20

popularity

25/25

security

12/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

cryptography django pyjwt

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/asymmetric-jwt-auth