Is gvl_timing safe to use?

gvl_timing has no known vulnerabilities on the latest version (0.3.3). DepScope rates its health at 61/100 (moderate risk).

What is the latest version of gvl_timing?

The latest version of gvl_timing is 0.3.3, released 2026-03-02.

Does gvl_timing have known vulnerabilities?

No known vulnerabilities on the latest version of gvl_timing.

Is gvl_timing deprecated?

No, gvl_timing is actively maintained. Latest release: 0.3.3 (2026-03-02).

What are alternatives to gvl_timing?

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

What license does gvl_timing use?

gvl_timing is licensed under MIT.

gvl_timing

rubygemsv0.3.3

Measure time spent in different GVL states

License MITpermissive6 versions0 deps22,426 weekly dl

jhawthorn/gvl_timing

/ 100

Health

use with caution

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

Moderate health score (61/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

10/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

API access

Get this data programmatically — free, no authentication.

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