Is sweet_notifications safe to use?

sweet_notifications has no known vulnerabilities on the latest version (1.1.2). DepScope rates its health at 51/100 (high risk).

What is the latest version of sweet_notifications?

The latest version of sweet_notifications is 1.1.2, released 2025-07-10.

Does sweet_notifications have known vulnerabilities?

No known vulnerabilities on the latest version of sweet_notifications.

Is sweet_notifications deprecated?

No, sweet_notifications is actively maintained. Latest release: 1.1.2 (2025-07-10).

What are alternatives to sweet_notifications?

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

What license does sweet_notifications use?

sweet_notifications is licensed under MIT.

sweet_notifications

rubygemsv1.1.2

Syntactic sugar for ActiveSupport::LogSubscriber for easy instrumentation and logging from third-party libraries.

License MITpermissive8 versions3 deps13,437 weekly dl

lautis/sweet_notifications

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (3)

activesupport railties request_store

API access

Get this data programmatically — free, no authentication.

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