Is api-clients/middleware-oauth1 safe to use?

api-clients/middleware-oauth1 has no known vulnerabilities on the latest version (4.0.0). DepScope rates its health at 30/100 (critical risk).

What is the latest version of api-clients/middleware-oauth1?

The latest version of api-clients/middleware-oauth1 is 4.0.0, released 2017-07-02.

Does api-clients/middleware-oauth1 have known vulnerabilities?

No known vulnerabilities on the latest version of api-clients/middleware-oauth1.

Is api-clients/middleware-oauth1 deprecated?

No, api-clients/middleware-oauth1 is actively maintained. Latest release: 4.0.0 (2017-07-02).

What are alternatives to api-clients/middleware-oauth1?

DepScope has no curated alternatives for api-clients/middleware-oauth1 at this time.

What license does api-clients/middleware-oauth1 use?

api-clients/middleware-oauth1 is licensed under MIT.

api-clients/middleware-oauth1

composerv4.0.0

Oauth1 middleware

License MITpermissive4 versions1 maintainers5 deps

php-api-clients/middleware-oauth1

/ 100

Health

use with caution

api-clients/[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 (5)

php api-clients/middleware api-clients/psr7-oauth1 guzzlehttp/psr7 wyrihaximus/ticking-promise

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/composer/api-clients/middleware-oauth1

Last updated · 2017-07-02T14:15:05+00:00