Is github.com/bme2003/cve-2018-6574 safe to use?

github.com/bme2003/cve-2018-6574 has no known vulnerabilities on the latest version (v0.0.0-20240619034840-57cd515985fd). DepScope rates its health at 42/100 (high risk).

What is the latest version of github.com/bme2003/cve-2018-6574?

The latest version of github.com/bme2003/cve-2018-6574 is v0.0.0-20240619034840-57cd515985fd, released 2024-06-19.

Does github.com/bme2003/cve-2018-6574 have known vulnerabilities?

No known vulnerabilities on the latest version of github.com/bme2003/cve-2018-6574.

Is github.com/bme2003/cve-2018-6574 deprecated?

No, github.com/bme2003/cve-2018-6574 is actively maintained. Latest release: v0.0.0-20240619034840-57cd515985fd (2024-06-19).

What are alternatives to github.com/bme2003/cve-2018-6574?

DepScope has no curated alternatives for github.com/bme2003/cve-2018-6574 at this time.

What license does github.com/bme2003/cve-2018-6574 use?

License information for github.com/bme2003/cve-2018-6574 is not declared in the registry metadata.

github.com/bme2003/cve-2018-6574

govv0.0.0-20240619034840-57cd515985fd

0 versions2 maintainers0 deps

bme2003/cve-2018-6574

/ 100

Health

safe to use

github.com/bme2003/[email protected] is safe to use (health: 42/100)

Health breakdown0 – 100

5/25

maintenance

0/20

popularity

25/25

security

9/15

maturity

3/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/go/github.com/bme2003/cve-2018-6574

Last updated · 2024-06-19T03:48:40Z