Is database_cleaner safe to use?

database_cleaner has no known vulnerabilities on the latest version (2.1.0). DepScope rates its health at 64/100 (moderate risk).

What is the latest version of database_cleaner?

The latest version of database_cleaner is 2.1.0, released 2024-10-25.

Does database_cleaner have known vulnerabilities?

No known vulnerabilities on the latest version of database_cleaner.

Is database_cleaner deprecated?

No, database_cleaner is actively maintained. Latest release: 2.1.0 (2024-10-25).

What are alternatives to database_cleaner?

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

What license does database_cleaner use?

database_cleaner is licensed under MIT.

database_cleaner

rubygemsv2.1.0

Strategies for cleaning databases. Can be used to ensure a clean slate for testing.

License MITpermissive20 versions1 deps12,137,378 weekly dl

DatabaseCleaner/database_cleaner

/ 100

Health

safe to use

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

Health breakdown0 – 100

5/25

maintenance

20/20

popularity

25/25

security

9/15

maturity

5/15

community

Vulnerabilities

none known

OSS Scorecard

OpenSSF security posture score

3.4/10

weak

Maintainer trust

Active maintainers (3m)

1

Contributors (12m)

1

Primary author dominance

100%

GitHub stars

2,961

single active maintainer 3msingle author dominance

Quality signals

Download trend

stable(0%)

Health History

Dependency Tree

License Audit

Dependencies (1)

database_cleaner-active_record

API access

Get this data programmatically — free, no authentication.

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