Is google-id-token safe to use?

google-id-token has no known vulnerabilities on the latest version (1.4.2). DepScope rates its health at 51/100 (high risk).

What is the latest version of google-id-token?

The latest version of google-id-token is 1.4.2, released 2017-09-11.

Does google-id-token have known vulnerabilities?

No known vulnerabilities on the latest version of google-id-token.

Is google-id-token deprecated?

No, google-id-token is actively maintained. Latest release: 1.4.2 (2017-09-11).

What are alternatives to google-id-token?

Popular alternatives to google-id-token in RubyGems include: jmespath, netrc, thread_safe, crass, tzinfo.

What license does google-id-token use?

google-id-token is licensed under APACHE-2.0.

google-id-token

rubygemsv1.4.2

Google ID Token utilities; currently just a parser/checker

License APACHE-2.0permissive6 versions1 deps10,989,699 weekly dl

google/google-id-token/

/ 100

Health

safe to use

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

Health breakdown0 – 100

0/25

maintenance

20/20

popularity

25/25

security

6/15

maturity

0/15

community

Vulnerabilities

none known

Quality signals

OSS Criticality

0.47medium

Health History

Dependency Tree

License Audit

Dependencies (1)

jwt

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/rubygems/google-id-token