Is github.com/hallazzang/labsafe-bypass safe to use?

github.com/hallazzang/labsafe-bypass has no known vulnerabilities on the latest version (v0.0.0-20180619141420-26675b3523fe). DepScope rates its health at 0/100 (unknown risk).

What is the latest version of github.com/hallazzang/labsafe-bypass?

The latest version of github.com/hallazzang/labsafe-bypass is v0.0.0-20180619141420-26675b3523fe, released 2018-06-19.

Does github.com/hallazzang/labsafe-bypass have known vulnerabilities?

No known vulnerabilities on the latest version of github.com/hallazzang/labsafe-bypass.

Is github.com/hallazzang/labsafe-bypass deprecated?

No, github.com/hallazzang/labsafe-bypass is actively maintained. Latest release: v0.0.0-20180619141420-26675b3523fe (2018-06-19).

What are alternatives to github.com/hallazzang/labsafe-bypass?

DepScope has no curated alternatives for github.com/hallazzang/labsafe-bypass at this time.

What license does github.com/hallazzang/labsafe-bypass use?

License information for github.com/hallazzang/labsafe-bypass is not declared in the registry metadata.

github.com/hallazzang/labsafe-bypass

govv0.0.0-20180619141420-26675b3523fe

0 versions1 maintainers0 deps1 weekly dl

hallazzang/labsafe-bypass

/ 100

Health

insufficient data

github.com/hallazzang/labsafe-bypass has limited data (1/6 signals) — verify manually before use

Limited information available for this package
Low health score (27/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/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/hallazzang/labsafe-bypass

Last updated · 2018-06-19T14:14:20Z