laravel-taxonomies VS laravel-medialibrary

There are a few for Laravel that I've used over the years (for example https://github.com/spatie/laravel-tags and https://github.com/myerscode/laravel-taxonomies). I think the reason that they are not common as generic packages, is that they need to be pretty locked into a specific storage, and that makes them less portable. The Laravel versions generally use Eloquent, so a storage has already been chosen.

I have it working ok for a single image using this idea but need the user to be able to add multiple images.

The current version as of writing this is 10.5.2 released 8 days ago.

Use this, i use it in all my projects.

An example of a good use of a polymorphic relationship can be seen in the Rails Active Storage module, which allows you to attach files to a model, and instead of duplicating the database columns and tables for each model that has attachments, there are two general tables: activestorage_attachments (attachments; relationship info) and activestorage_blobs (blobs; file info). A model can have one or many attachments (has_one_attachment and has_many_attachments, both can be used more than once depending on your needs), an attachment belongs to a record (record_id and record_type) and belongs to a blob (blob_id), and blobs have one attachment. You can access an attachment attribute on the related model like so, user.avatar # has_one_attachment(:avatar); or for many attachments of the same type, user.photos # an array of attachments; has_many_attachments(:photos). There’s a Laravel package similar to this called spatie/laravel-medialibrary.

For storing files and associating them with models, I can highly recommend Spatie's Media Library. Used it in a project recently and haven't had any hassle with it.