Is byte-triggers safe to use?

byte-triggers has no known vulnerabilities on the latest version (0.4.1). DepScope rates its health at 33/100 (critical risk).

What is the latest version of byte-triggers?

The latest version of byte-triggers is 0.4.1, released 2024-09-11.

Does byte-triggers have known vulnerabilities?

No known vulnerabilities on the latest version of byte-triggers.

Is byte-triggers deprecated?

No, byte-triggers is actively maintained. Latest release: 0.4.1 (2024-09-11).

What are alternatives to byte-triggers?

Popular alternatives to byte-triggers in PyPI include: boto3, packaging, urllib3, certifi, idna.

What license does byte-triggers use?

byte-triggers is licensed under MIT.

byte-triggers

pypiv0.4.1

Provides byte (0 to 255) triggers on serial/parallel ports and on LSL streams.

License MITpermissive5 versions34 deps8 weekly dl

/ 100

Health

use with caution

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

Low health score (33/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/byte-triggers