Is sequel_postgresql_triggers safe to use?

sequel_postgresql_triggers has no known vulnerabilities on the latest version (1.6.0). DepScope rates its health at 44/100 (high risk).

What is the latest version of sequel_postgresql_triggers?

The latest version of sequel_postgresql_triggers is 1.6.0, released 2024-01-18.

Does sequel_postgresql_triggers have known vulnerabilities?

No known vulnerabilities on the latest version of sequel_postgresql_triggers.

Is sequel_postgresql_triggers deprecated?

No, sequel_postgresql_triggers is actively maintained. Latest release: 1.6.0 (2024-01-18).

What are alternatives to sequel_postgresql_triggers?

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

What license does sequel_postgresql_triggers use?

sequel_postgresql_triggers is licensed under MIT.

sequel_postgresql_triggers

rubygemsv1.6.0

Database enforced timestamps, immutable columns, counter/sum caches, and touch propogation

License MITpermissive13 versions1 deps22,469 weekly dl

jeremyevans/sequel_postgresql_triggers

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

10/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

sequel

API access

Get this data programmatically — free, no authentication.

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