Is spree_emails safe to use?

spree_emails has no known vulnerabilities on the latest version (5.4.2). DepScope rates its health at 70/100 (moderate risk).

What is the latest version of spree_emails?

The latest version of spree_emails is 5.4.2, released 2026-04-27.

Does spree_emails have known vulnerabilities?

No known vulnerabilities on the latest version of spree_emails.

Is spree_emails deprecated?

No, spree_emails is actively maintained. Latest release: 5.4.2 (2026-04-27).

What are alternatives to spree_emails?

Popular alternatives to spree_emails in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does spree_emails use?

spree_emails is licensed under BSD-3-Clause.

spree_emails

rubygemsv5.4.2

Optional transactional emails for Spree such as Order placed or Shipment notification emails

License BSD-3-Clausepermissive20 versions1 deps237 weekly dl

spree/spree/tree/v5.4.2

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

8/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

spree

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/spree_emails

spree_emails

rubygemsv5.4.2

Optional transactional emails for Spree such as Order placed or Shipment notification emails

License BSD-3-Clausepermissive20 versions1 deps237 weekly dl

spree/spree/tree/v5.4.2

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

8/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

spree

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/spree_emails