Is await-ccb safe to use?

await-ccb has no known vulnerabilities on the latest version (0.1.3). DepScope rates its health at 30/100 (critical risk).

What is the latest version of await-ccb?

The latest version of await-ccb is 0.1.3, released 2018-04-24.

Does await-ccb have known vulnerabilities?

No known vulnerabilities on the latest version of await-ccb.

Is await-ccb deprecated?

No, await-ccb is actively maintained. Latest release: 0.1.3 (2018-04-24).

What are alternatives to await-ccb?

Popular alternatives to await-ccb in PyPI include: boto3, packaging, certifi, urllib3, idna.

What license does await-ccb use?

await-ccb is licensed under MIT.

await-ccb

pypiv0.1.3

Waits for Google Cloud Container Build to complete

License MITpermissive4 versions1 maintainers4 deps9 weekly dl

thedyrt/await-ccb

/ 100

Health

use with caution

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

Moderate health score (30/100) — verify manually

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

none known

Health History

Dependency Tree

License Audit

Dependencies (4)

google-auth google-auth-httplib2 google-api-python-client docopt

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/pypi/await-ccb