Is j6s/flow-apcu-with-fallback safe to use?

j6s/flow-apcu-with-fallback has no known vulnerabilities on the latest version (2.0.0). DepScope rates its health at 30/100 (critical risk).

What is the latest version of j6s/flow-apcu-with-fallback?

The latest version of j6s/flow-apcu-with-fallback is 2.0.0, released 2021-01-31.

Does j6s/flow-apcu-with-fallback have known vulnerabilities?

No known vulnerabilities on the latest version of j6s/flow-apcu-with-fallback.

Is j6s/flow-apcu-with-fallback deprecated?

No, j6s/flow-apcu-with-fallback is actively maintained. Latest release: 2.0.0 (2021-01-31).

What are alternatives to j6s/flow-apcu-with-fallback?

DepScope has no curated alternatives for j6s/flow-apcu-with-fallback at this time.

What license does j6s/flow-apcu-with-fallback use?

j6s/flow-apcu-with-fallback is licensed under MIT.

j6s/flow-apcu-with-fallback

composerv2.0.0

Package that provides an APCu cache backend that falls back to a given fallback if the APCu extension is not installed.

License MITpermissive4 versions1 maintainers2 deps

j6s/flow-apcu-fallback-cache

/ 100

Health

use with caution

j6s/[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 (2)

php neos/cache

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/composer/j6s/flow-apcu-with-fallback

Last updated · 2021-01-31T16:25:48+00:00