Is binding_of_caller safe to use?

binding_of_caller has no known vulnerabilities on the latest version (2.0.0). DepScope rates its health at 71/100 (moderate risk).

What is the latest version of binding_of_caller?

The latest version of binding_of_caller is 2.0.0, released 2026-02-15.

Does binding_of_caller have known vulnerabilities?

No known vulnerabilities on the latest version of binding_of_caller.

Is binding_of_caller deprecated?

No, binding_of_caller is actively maintained. Latest release: 2.0.0 (2026-02-15).

What are alternatives to binding_of_caller?

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

What license does binding_of_caller use?

binding_of_caller is licensed under MIT.

binding_of_caller

rubygemsv2.0.0

Provides the Binding#of_caller method. Using binding_of_caller we can grab bindings from higher up the call stack and evaluate code in that context. Allows access to bindings arbitrarily far up the call stack, not limited to just the immediate caller. Recommended for use only in debugging situations. Do not use this in production apps.

License MITpermissive20 versions1 deps2,200,549 weekly dl

banister/binding_of_caller

/ 100

Health

safe to use

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

Health breakdown0 – 100

20/25

maintenance

17/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.42medium

Health History

Dependency Tree

License Audit

Dependencies (1)

debug_inspector

API access

Get this data programmatically — free, no authentication.

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