Is vagrant-proxyconf safe to use?

vagrant-proxyconf has no known vulnerabilities on the latest version (2.0.10). DepScope rates its health at 48/100 (high risk).

What is the latest version of vagrant-proxyconf?

The latest version of vagrant-proxyconf is 2.0.10, released 2020-07-03.

Does vagrant-proxyconf have known vulnerabilities?

No known vulnerabilities on the latest version of vagrant-proxyconf.

Is vagrant-proxyconf deprecated?

No, vagrant-proxyconf is actively maintained. Latest release: 2.0.10 (2020-07-03).

What are alternatives to vagrant-proxyconf?

Popular alternatives to vagrant-proxyconf in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does vagrant-proxyconf use?

vagrant-proxyconf is licensed under MIT.

vagrant-proxyconf

rubygemsv2.0.10

A Vagrant plugin that configures the virtual machine to use proxy servers

License MITpermissive20 versions0 deps108,534 weekly dl

tmatilai/vagrant-proxyconf

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/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/rubygems/vagrant-proxyconf