Is aauth-signing safe to use?

aauth-signing has no known vulnerabilities on the latest version (0.1.2). DepScope rates its health at 53/100 (high risk).

What is the latest version of aauth-signing?

The latest version of aauth-signing is 0.1.2, released 2026-04-22.

Does aauth-signing have known vulnerabilities?

No known vulnerabilities on the latest version of aauth-signing.

Is aauth-signing deprecated?

No, aauth-signing is actively maintained. Latest release: 0.1.2 (2026-04-22).

What are alternatives to aauth-signing?

Popular alternatives to aauth-signing in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does aauth-signing use?

aauth-signing is licensed under MIT.

aauth-signing

pypiv0.1.2

HTTP Message Signing (RFC 9421 + draft-hardt-httpbis-signature-key) for AAuth

License MITpermissive3 versions2 deps

/ 100

Health

use with caution

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

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

cryptography PyJWT

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/aauth-signing

aauth-signing

pypiv0.1.2

HTTP Message Signing (RFC 9421 + draft-hardt-httpbis-signature-key) for AAuth

License MITpermissive3 versions2 deps

/ 100

Health

use with caution

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

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

25/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

cryptography PyJWT

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/aauth-signing