Is brightcove-api safe to use?

brightcove-api has no known vulnerabilities on the latest version (1.0). DepScope rates its health at 27/100 (critical risk).

What is the latest version of brightcove-api?

The latest version of brightcove-api is 1.0, released 2017-10-30.

Does brightcove-api have known vulnerabilities?

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

Is brightcove-api deprecated?

No, brightcove-api is actively maintained. Latest release: 1.0 (2017-10-30).

What are alternatives to brightcove-api?

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

What license does brightcove-api use?

brightcove-api is licensed under MIT.

brightcove-api

pypiv1.0

SDK for the Brightcove Analytics API

License MITpermissive1 versions1 maintainers0 deps

nickymikail/brightcove-api

/ 100

Health

use with caution

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

Low health score (27/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/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/pypi/brightcove-api