Weave Code
Boredom Laravel Package
lara-zeus/boredom
A Laravel wrapper for the Bored API that suggests things to do when you're bored. Fetch random activities filtered by type, participants, price, or accessibility through a clean, simple, expressive interface.
lara-zeus/boredom is a lightweight Laravel package from the Lara Zeus ecosystem that adds playful, engaging touches to your application — the small details that keep users from getting bored. It follows the conventions of the Lara Zeus family: quick Composer installation, sensible defaults, and configuration that stays out of your way.
- Plug-and-play setup with an auto-discovered service provider
- Publishable config for fast customization
- Blade-ready components that fit any existing layout
- Laravel-native — no extra build step or frontend tooling
- Actively maintained alongside the wider Lara Zeus suite
Frequently asked questions about Boredom
- How do I install lara-zeus/boredom in a Laravel Filament application?
- Install it with composer require lara-zeus/boredom. Then verify the shipped provider class namespace against the package's src directory, register it in your panel provider's boot() method, clear Filament's component cache, and smoke-test a UserResource table plus a comment thread. The whole integration is small enough that half a day is a realistic ceiling.
- Does lara-zeus/boredom use the Bored API to suggest activities, or is it about avatars?
- The primary description says it provides Boring Avatars as the default avatar provider in FilamentPHP v3, while older copy mentions random activity suggestions from the Bored API and appears to be stale. The vendor is a Filament plugin shop and the 3.0.0 changelog only mentions Filament 5 support, both of which point to the avatar reading. Confirm against composer.json and src/ before you commit, because the two readings change effort, privacy impact, and blast radius entirely.
- Which Filament and Laravel versions does lara-zeus/boredom support?
- It targets Filament v3+ panels, Laravel 11/12, and PHP 8.2+, and it is out of scope for Filament v2 and for non-Filament surfaces like Blade helpers or API resources. Major releases exist to track Filament majors, so a 3.0.0 whose only substantive change is Filament 5 support strongly implies the 2.x line is unmaintained. Check the composer.json constraint to see whether the version you need installs against your panel's Filament major at all.
- How do I register Boring Avatars as the default avatar provider in a Filament panel?
- Call Filament::setAvatarProvider() inside the boot() method of your PanelProvider, not register(). Verify the exact FQCN of the shipped provider against the package's src directory first, since the overview does not document it. boot() is the right seam because panel configuration there runs after all plugins have been registered.
- Does lara-zeus/boredom make external HTTP requests or generate avatars locally?
- For the avatar reading, the expectation is local deterministic SVG seeded from a user field, which means no vendor egress and a clean compliance story. That argument only holds if the provider renders SVG in-process rather than calling a hosted Boring Avatars endpoint, so read the provider source to confirm. If it does make outbound calls, treat user names as data leaving your infrastructure and check it against your privacy policy.
- What field is used as the avatar seed, and can I change it?
- The seed is likely the user's name or email, but the package overview does not document which, and it may or may not be configurable. Read the provider class and any published config file to confirm before relying on it. The seed choice matters if names are considered personal data in your jurisdiction.
- What happens when a user has a null or empty name?
- This behavior is undocumented, so test it explicitly with a record that has a null or blank name. You will likely get an empty-string seed avatar, a placeholder, or possibly an exception. The most probable failure mode is a silently blank avatar rather than a crash, which is cheap to fix but expensive to notice in production.
- Does lara-zeus/boredom ship a config file I can customize?
- Several Lara Zeus packages ship publishable config, but the overview does not confirm one here. After installing, check for a config file and any vendor:publish tags, then inspect what it exposes for palette or variant customization. If a config exists, publish it and commit the file so your customizations survive deploys.
- Is lara-zeus/boredom safe to use in production?
- It is architecturally shallow, touching only Filament's avatar provider seam, so the technical risk is low. The continuity risk is real: one maintainer, a small star count, no dependents, no SLA, and no security-backport commitment, plus major versions pinned to Filament majors. Contain that by keeping it at a single seam and never referencing LaraZeus classes from views, resources, or the User model, so a roughly 50-line in-house AvatarProvider can replace it if it stalls.
- How do I remove lara-zeus/boredom cleanly, and what are the alternatives?
- Remove the setAvatarProvider() call from your PanelProvider, delete any published config or assets, clear Filament's component cache, then run composer remove lara-zeus/boredom. Check whether the publish step left views behind, since that can fail silently. Alternatives are a small in-house AvatarProvider implementing Filament's contract with initials or deterministic SVG, or any other maintained avatar provider you can register the same way.
Weaver
How can I help you explore Laravel packages today?