Should we mark this package as EOL?

The underlying library is no longer supported:

Since no one is actively developing this I'm convinced no one will do the effort of rewriting it to use the referenced library.

@DavertMik, we should mark it as EOL on packagist and in the readme. That way people still using it get warnings and know they should be moving away from this if their code needs to be maintained for the foreseeable future.

Check the package's Packagist listing and README to identify where the project status is presented. Confirm how EOL status and maintenance warnings are represented there, then update both locations so users are clearly told to move away from the package.

Written by the indexing model from the issue text.