Is aim-records safe to use?

aim-records has no known vulnerabilities on the latest version (0.0.1). DepScope rates its health at 25/100 (critical risk).

What is the latest version of aim-records?

The latest version of aim-records is 0.0.1, released 2020-03-28.

Does aim-records have known vulnerabilities?

No known vulnerabilities on the latest version of aim-records.

Is aim-records deprecated?

No, aim-records is actively maintained. Latest release: 0.0.1 (2020-03-28).

What are alternatives to aim-records?

Popular alternatives to aim-records in PyPI include: boto3, packaging, urllib3, idna, certifi.

What license does aim-records use?

aim-records is licensed under MIT.

aim-records

pypiv0.0.1

An event-oriented data format which utilizes Protocol Buffers

License MITpermissive1 versions1 deps2 weekly dl

/ 100

Health

use with caution

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

Moderate health score (25/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

protobuf

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/aim-records

aim-records

pypiv0.0.1

An event-oriented data format which utilizes Protocol Buffers

License MITpermissive1 versions1 deps2 weekly dl

/ 100

Health

use with caution

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

Moderate health score (25/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

protobuf

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/aim-records