Is resultsdb-api safe to use?

resultsdb-api has no known vulnerabilities on the latest version (2.1.6). DepScope rates its health at 59/100 (high risk).

What is the latest version of resultsdb-api?

The latest version of resultsdb-api is 2.1.6, released 2026-03-26.

Does resultsdb-api have known vulnerabilities?

No known vulnerabilities on the latest version of resultsdb-api.

Is resultsdb-api deprecated?

No, resultsdb-api is actively maintained. Latest release: 2.1.6 (2026-03-26).

What are alternatives to resultsdb-api?

Popular alternatives to resultsdb-api in PyPI include: boto3, packaging, urllib3, idna, requests.

What license does resultsdb-api use?

resultsdb-api is licensed under GNU General Public v2 or later (GPLv2+).

resultsdb-api

pypiv2.1.6

Library for simplifying the communication with ResultsDB

License GNU General Public v2 or later (GPLv2+)12 versions1 maintainers2 deps137 weekly dl

/ 100

Health

use with caution

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

Moderate health score (59/100) — verify manually

Health breakdown0 – 100

20/25

maintenance

3/20

popularity

25/25

security

9/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

requests simplejson

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/resultsdb-api