Is aiofiles38 safe to use?

aiofiles38 has no known vulnerabilities on the latest version (0.5.0.dev0). DepScope rates its health at 27/100 (critical risk).

What is the latest version of aiofiles38?

The latest version of aiofiles38 is 0.5.0.dev0, released 2019-12-12.

Does aiofiles38 have known vulnerabilities?

No known vulnerabilities on the latest version of aiofiles38.

Is aiofiles38 deprecated?

No, aiofiles38 is actively maintained. Latest release: 0.5.0.dev0 (2019-12-12).

What are alternatives to aiofiles38?

Popular alternatives to aiofiles38 in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does aiofiles38 use?

aiofiles38 is licensed under Apache 2.0.

aiofiles38

pypiv0.5.0.dev0

this will be removed after the origin aiofiles38 supports new versions of Python

License Apache 2.0permissive1 versions1 maintainers0 deps

kasheemlew/aiofiles

/ 100

Health

use with caution

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

Low health score (27/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

⚠ Possible typosquat

Name is close to a popular package. Targets:

aiofiles (close_name dist 2)

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/aiofiles38