Is can-j1939-ttpsc safe to use?

can-j1939-ttpsc has no known vulnerabilities on the latest version (1.0.4). DepScope rates its health at 30/100 (critical risk).

What is the latest version of can-j1939-ttpsc?

The latest version of can-j1939-ttpsc is 1.0.4, released 2024-05-24.

Does can-j1939-ttpsc have known vulnerabilities?

No known vulnerabilities on the latest version of can-j1939-ttpsc.

Is can-j1939-ttpsc deprecated?

No, can-j1939-ttpsc is actively maintained. Latest release: 1.0.4 (2024-05-24).

What are alternatives to can-j1939-ttpsc?

Popular alternatives to can-j1939-ttpsc in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does can-j1939-ttpsc use?

can-j1939-ttpsc is licensed under MIT.

can-j1939-ttpsc

pypiv1.0.4

Fork of SAE J1939 stack implementation, originally created by Juergen Heilgemeir

License MITpermissive3 versions1 maintainers3 deps15 weekly dl

ttpscmolinaf/python-can-j1939

/ 100

Health

use with caution

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

Moderate health score (30/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

python-can numpy pytest

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/can-j1939-ttpsc