Is best_in_place safe to use?

best_in_place has no known vulnerabilities on the latest version (4.0.0). DepScope rates its health at 53/100 (high risk).

What is the latest version of best_in_place?

The latest version of best_in_place is 4.0.0, released 2024-08-15.

Does best_in_place have known vulnerabilities?

No known vulnerabilities on the latest version of best_in_place.

Is best_in_place deprecated?

No, best_in_place is actively maintained. Latest release: 4.0.0 (2024-08-15).

What are alternatives to best_in_place?

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

What license does best_in_place use?

License information for best_in_place is not declared in the registry metadata.

best_in_place

rubygemsv4.0.0

BestInPlace is a jQuery script and a Rails helper that provide the method best_in_place to display any object field easily editable for the user by just clicking on it. It supports input data, text data, boolean data and custom dropdown data. It works with RESTful controllers.

20 versions2 deps169,394 weekly dl

http://github.com/bernat/best_in_place

/ 100

Health

use with caution

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

Moderate health score (53/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

14/20

popularity

25/25

security

9/15

maturity

5/15

community

0/15

popularity_floor

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

actionpack railties

API access

Get this data programmatically — free, no authentication.

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