Is large_text_field safe to use?

large_text_field has no known vulnerabilities on the latest version (1.3.0). DepScope rates its health at 58/100 (high risk).

What is the latest version of large_text_field?

The latest version of large_text_field is 1.3.0, released 2025-06-09.

Does large_text_field have known vulnerabilities?

No known vulnerabilities on the latest version of large_text_field.

Is large_text_field deprecated?

No, large_text_field is actively maintained. Latest release: 1.3.0 (2025-06-09).

What are alternatives to large_text_field?

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

What license does large_text_field use?

large_text_field is licensed under MIT.

large_text_field

rubygemsv1.3.0

Large text fields are kept in a central table, and polymorphically associated with your models. Access and assignment should behave as if it was a column on the same table.

License MITpermissive11 versions2 deps118,352 weekly dl

invoca/large_text_field

58

/ 100

Health

safe to use

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

Health breakdown0 – 100

10/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

0

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

invoca-utils rails

API access

Get this data programmatically — free, no authentication.

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