Is api-skeletons/correct-utf8-encoding safe to use?

api-skeletons/correct-utf8-encoding has no known vulnerabilities on the latest version (1.0.0). DepScope rates its health at 27/100 (critical risk).

What is the latest version of api-skeletons/correct-utf8-encoding?

The latest version of api-skeletons/correct-utf8-encoding is 1.0.0, released 2019-01-19.

No known vulnerabilities on the latest version of api-skeletons/correct-utf8-encoding.

No, api-skeletons/correct-utf8-encoding is actively maintained. Latest release: 1.0.0 (2019-01-19).

DepScope has no curated alternatives for api-skeletons/correct-utf8-encoding at this time.

api-skeletons/correct-utf8-encoding is licensed under MIT.

composerv1.0.0

Correct badly encoded and multiple encoded UTF8 characters by examining each byte in a string.

License MITpermissive1 versions1 maintainers0 deps

/ 100

Health

use with caution

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

Health breakdown0 – 100

0/25

maintenance

0/20

popularity

25/25

security

0/15

maturity

2/15

community

Vulnerabilities

none known

API access

Get this data programmatically — free, no authentication.

curl https://depscope.dev/api/check/composer/api-skeletons/correct-utf8-encoding

Last updated · 2019-01-19T23:51:00+00:00