Weave Code
Statamic Laravel Packages Laravel Package
handmadeweb/statamic-laravel-packages
Statamic addon from Handmade Web that brings Laravel package management into your Statamic control panel, so you can browse installed packages and inspect their details without leaving the CP. Install quickly via Composer; ideal for teams standardizing Laravel integrations.
Adds "quick access links" and permissions to Statamic, for popular Laravel (Horizon, Nova, Telescope) packages.
Frequently asked questions about Statamic Laravel Packages
- What does the handmadeweb/statamic-laravel-packages addon actually do?
- It is a Statamic addon that adds quick access links and permission controls to the Statamic control panel for popular Laravel packages such as Horizon, Nova, and Telescope. Instead of hunting for URLs, developers and editors can jump straight to those tools from the CP. It also lets you gate those links behind permissions so only the right roles see them. It is a convenience and access-control layer, not a replacement for the underlying packages.
- How do I install handmadeweb/statamic-laravel-packages with Composer?
- Installation is Composer-native: require the package in the same Laravel project as your Statamic site and register it as a Statamic addon following its README. Because it is an addon, it belongs in an application that already has statamic/cms installed. Review the lockfile diff before committing and pin the version explicitly. There is no separate build step implied.
- Does this package work with Statamic 3.4, and which Laravel and PHP versions does it need?
- Release 1.0.4 ships a composer.json manifest targeting Statamic 3.4, so that is the declared compatibility surface. The package does not publish a separate Laravel or PHP matrix, so the effective constraint is the intersection of Statamic 3.4's own requirements and your application's. Confirm that your statamic/cms and laravel/framework constraints both admit the manifest before installing. Treat the 3.4 manifest as a claim to verify in staging, not a guarantee.
- Can I use this addon in a plain Laravel app without Statamic?
- No. It is a Statamic addon and its dependency surface assumes statamic/cms is present, which the Statamic 3.4 manifest makes explicit. For a pure Laravel application with no CMS, the package is out of scope and you would simply link to Horizon, Nova, or Telescope yourself. The value it adds is control panel integration and permissions, which only exist inside Statamic.
- How do the permissions for Horizon, Nova, and Telescope work in this addon?
- The addon provides permissions that control who can see and follow the quick access links to those Laravel tools from the Statamic control panel. You assign them to roles or users the same way you manage other Statamic permissions. Note that the addon governs visibility of the link, not authorization inside Horizon, Nova, or Telescope, which keep their own gates. Use both layers together for real access control.
- Is version 1.0.4 stable enough to run in production?
- It is early-life software: a 1.0.4 patch release with a cadence that looks active but immature. That is not disqualifying for a convenience addon, but treat it as something to verify rather than assume. Install it in staging, exercise the control panel surfaces it touches, and pin the exact version in composer.json. Because the blast radius is limited to CP links and permissions, the risk profile is lower than a package that mutates content.
- Does this addon support Statamic 4 or 5?
- The published manifest targets Statamic 3.4 only, so nothing is declared for 3.3, 4.x, or 5.x. The maintainers appear to ship separate manifests per Statamic minor, which means a future Statamic minor or major likely requires a matching package release. Pin explicitly in composer.json and check for a compatible tag before upgrading your host. Do not rely on floating constraints to resolve this for you.
- What happens to this addon when I upgrade Statamic to a new minor or major version?
- Expect an upgrade tax: because compatibility is declared through per-Statamic-minor composer manifests, the package needs a release each time Statamic bumps a minor. If the maintainer lags, your Statamic upgrade window is partly gated on their responsiveness. Sequence the work as two separate changes: land the Statamic upgrade first with your content model verified, then add or update the addon. This keeps failure attribution clean.
- Who maintains handmadeweb/statamic-laravel-packages and what is the bus factor risk?
- It is maintained by Handmade Web, a small agency-style maintainer, which implies a community support model rather than a vendor SLA. The package notes publish no LTS or support-window commitment. The practical risk is bus factor: a small-maintainer addon can go quiet, and because this one ships per-Statamic-minor manifests, a quiet maintainer becomes your upgrade blocker. Track upstream releases and be prepared to fork or drop the addon if it falls behind.
- How should I test this addon before deploying it to production?
- Install it in staging on a host already running Statamic 3.4 with a working test suite. Exercise the specific control panel surfaces the addon adds, verify that permission gating behaves correctly for each role you care about, and run a content-integrity check on the relevant entries and fields. Promote to production behind a reversible deploy with a reviewed lockfile. Avoid combining the addon install with a Statamic upgrade in a single release.
Weaver
How can I help you explore Laravel packages today?