Is acts_as_archival safe to use?

acts_as_archival has no known vulnerabilities on the latest version (2.1.0). DepScope rates its health at 50/100 (high risk).

What is the latest version of acts_as_archival?

The latest version of acts_as_archival is 2.1.0, released 2022-06-21.

Does acts_as_archival have known vulnerabilities?

No known vulnerabilities on the latest version of acts_as_archival.

Is acts_as_archival deprecated?

No, acts_as_archival is actively maintained. Latest release: 2.1.0 (2022-06-21).

What are alternatives to acts_as_archival?

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

What license does acts_as_archival use?

acts_as_archival is licensed under MIT.

acts_as_archival

rubygemsv2.1.0

*Atomic archiving/unarchiving for ActiveRecord-based apps* We had the problem that acts_as_paranoid and similar plugins/gems always work on a record by record basis and made it very difficult to restore records atomically (or archive them, for that matter). Because the archive and unarchive methods are in transactions, and every archival record involved gets the same archive number upon archiving, you can easily restore or remove an entire set of records without having to worry about partial d

License MITpermissive17 versions1 deps212,589 weekly dl

http://github.com/expectedbehavior/acts_as_archival

/ 100

Health

use with caution

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

Moderate health score (50/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (1)

activerecord

API access

Get this data programmatically — free, no authentication.

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