Is api-clients/middleware-token-authorization safe to use?

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

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

The latest version of api-clients/middleware-token-authorization is 3.0.0, released 2017-07-02.

Does api-clients/middleware-token-authorization have known vulnerabilities?

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

Is api-clients/middleware-token-authorization deprecated?

No, api-clients/middleware-token-authorization is actively maintained. Latest release: 3.0.0 (2017-07-02).

What are alternatives to api-clients/middleware-token-authorization?

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

What license does api-clients/middleware-token-authorization use?

api-clients/middleware-token-authorization is licensed under MIT.

api-clients/middleware-token-authorization

composerv3.0.0

Token authorization middleware

License MITpermissive3 versions1 maintainers2 deps

php-api-clients/middleware-token-authorization

30

/ 100

Health

use with caution

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

Low health score (30/100)

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

3/15

maturity

2/15

community

Vulnerabilities

0

none known

Health History

Dependency Tree

License Audit

Dependencies (2)

php api-clients/middleware

API access

Get this data programmatically — free, no authentication.

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

Last updated · 2017-07-02T14:14:54+00:00