Is incognia_api safe to use?

incognia_api has no known vulnerabilities on the latest version (3.1.0). DepScope rates its health at 62/100 (moderate risk).

What is the latest version of incognia_api?

The latest version of incognia_api is 3.1.0, released 2026-04-17.

Does incognia_api have known vulnerabilities?

No known vulnerabilities on the latest version of incognia_api.

Is incognia_api deprecated?

No, incognia_api is actively maintained. Latest release: 3.1.0 (2026-04-17).

What are alternatives to incognia_api?

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

What license does incognia_api use?

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

incognia_api

rubygemsv3.1.0

Official Ruby lib for communicating with Incognia API

20 versions2 deps148 weekly dl

inloco/incognia-ruby

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

faraday faraday-net_http_persistent

API access

Get this data programmatically — free, no authentication.

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

incognia_api

rubygemsv3.1.0

Official Ruby lib for communicating with Incognia API

20 versions2 deps148 weekly dl

inloco/incognia-ruby

/ 100

Health

safe to use

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

Health breakdown0 – 100

25/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

0/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

faraday faraday-net_http_persistent

API access

Get this data programmatically — free, no authentication.

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