Is vagrant-triggers safe to use?

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

What is the latest version of vagrant-triggers?

The latest version of vagrant-triggers is 0.5.3, released 2016-04-09.

Does vagrant-triggers have known vulnerabilities?

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

Is vagrant-triggers deprecated?

No, vagrant-triggers is actively maintained. Latest release: 0.5.3 (2016-04-09).

What are alternatives to vagrant-triggers?

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

What license does vagrant-triggers use?

vagrant-triggers is licensed under MIT.

vagrant-triggers

rubygemsv0.5.3

This plugin allow the definition of arbitrary scripts that will run on the host before and/or after Vagrant commands.

License MITpermissive14 versions1 deps246,218 weekly dl

emyl/vagrant-triggers

/ 100

Health

use with caution

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

Moderate health score (48/100) — verify manually

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

Dependencies (1)

bundler

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/vagrant-triggers