This is a question of Seeds vs Migrations (vs any other alternatives there may be!)
Let's say we have a table 'submission_types' of which can not ever be modified by the app itself. For example these types may represent 'video', 'image', 'audio'. This data is necessary for the correct functioning and hypothetical submission of either a video, image or audio file to the site.
Where does the insertion of this data go, as it must be present when the app is running (regardless of dev/production environments)? Should you use Laravel's Seeders? - Seems to me like they are geared towards loading up your database with test data... Or should you use migrations? - Seems that people recommend to keep inserts away from migrations. (Or do you insert the data manually... of course not). To re-iterate, this data must be present under all circumstances and will not be modified by any business logic, ever - this is static data.
This question seems related.
PS: In the future you may want to add some more types to the table, so doing this via migrations seems... less than ideal?