Is byted-trigger-eval safe to use?

byted-trigger-eval has no known vulnerabilities on the latest version (0.0.1). DepScope rates its health at 56/100 (high risk).

What is the latest version of byted-trigger-eval?

The latest version of byted-trigger-eval is 0.0.1, released 2026-02-12.

No known vulnerabilities on the latest version of byted-trigger-eval.

No, byted-trigger-eval is actively maintained. Latest release: 0.0.1 (2026-02-12).

Popular alternatives to byted-trigger-eval in PyPI include: boto3, packaging, certifi, urllib3, idna.

byted-trigger-eval is licensed under MIT.

pypiv0.0.1

This is a reserved placeholder package to mitigate dependency confusion risks.

License MITpermissive1 versions1 maintainers0 deps

56

/ 100

Health

safe to use

[email protected] is safe to use (health: 56/100)

Health breakdown0 – 100

20/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

0

none known

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/byted-trigger-eval