Weave Code
Weaver
Helps Laravel developers discover, compare, and choose open-source packages. See popularity, security, maintainers, and scores at a glance to make better decisions.
Feedback
Share your thoughts, report bugs, or suggest improvements.
Subject
Message
Shorturl Bundle

Shorturl Bundle Laravel Package

fabstei/shorturl-bundle

A Symfony bundle for adding short URL support to your applications. It provides services for generating short codes and resolving them back to their original destinations, with simple configuration for dropping into existing Symfony projects.

View on GitHub
Deep Wiki
Context7

fabstei/shorturl-bundle provides a lightweight Symfony integration for creating and resolving shortened URLs. It includes ready-to-use routing and controller support, making it easy to map short codes to destination URLs and redirect visitors with minimal configuration.

  • Short code generation for compact URL mapping
  • Symfony routing and controller for redirect handling
  • Doctrine-backed storage for persisted short URLs
  • Configurable code length and URL settings
  • Simple bundle registration and setup
Frequently asked questions about Shorturl Bundle
Is fabstei/shorturl-bundle compatible with Laravel?
No. fabstei/shorturl-bundle is a Symfony2 bundle built around Symfony's DependencyInjection, routing, and Doctrine ORM conventions. It has no Laravel service provider, config publishing, or Eloquent integration. Installing it in a Laravel app would not give you working short URL features.
Can I install fabstei/shorturl-bundle with Composer in a Laravel project?
You should not attempt it. The package targets Symfony 2.x-era APIs and old PHP versions, so Composer will likely fail on constraint conflicts or pull in an unsupported symfony/http-kernel tree. Even if installation succeeded, the bundle would not register with Laravel's container or routing.
Which Symfony and PHP versions does fabstei/shorturl-bundle support?
It is a Symfony2 bundle, consistent with Symfony 2.0 through 2.8-era APIs and PHP 5.3 to 5.6 vintage. It is not compatible with Symfony 5, 6, or 7, nor with PHP 8.x. Modern Laravel versions require PHP versions far beyond what this bundle was written for.
Is fabstei/shorturl-bundle maintained or archived?
The repository is archived and has had no releases for roughly a decade. There is no security patching, no PHP compatibility work, and no issue triage. Treat it as reference-only material rather than a dependency.
How do I create and manage short URLs in Laravel without this bundle?
Build a Laravel-native implementation with a short_urls table, an Eloquent model, a short-code generator service, and a redirect controller. Add a route such as Route::get('/s/{code}') that resolves the code and returns a 302. This is a small, well-understood domain and usually takes days, not weeks.
What security risks come with using an old URL shortener bundle?
URL shorteners are a classic open-redirect and abuse vector, so redirect logic must validate schemes and handle headers carefully. This bundle's 2014-era code has not been audited for modern threats and receives no security patches. Absence of published CVEs for an abandoned package does not mean it is safe.
Does fabstei/shorturl-bundle work on PHP 8?
No. The bundle is from the PHP 5.3 to 5.6 era and was not written for PHP 8.x compatibility. You would encounter deprecated APIs and type issues even outside Laravel. Modern Laravel applications cannot use it as-is.
What are good alternatives to fabstei/shorturl-bundle for Laravel URL shortening?
For most teams, a small custom Laravel implementation is the best fit because the domain is simple: store a code, resolve it, redirect. Managed services such as Bitly or Dub are reasonable if you need analytics, custom domains, and click tracking without building them. Choose based on requirements like expiration, per-tenant namespacing, and data residency.
Can I copy code from fabstei/shorturl-bundle into my Laravel project?
Check the license file first, because an unclear license blocks verbatim reuse. Even with a permissive license, the code is Symfony2-specific and would need substantial rewriting for Laravel. It is usually better to read it for design ideas and then implement your own model, service, and controller.
How much effort is it to build a Laravel-native short URL feature instead of using this bundle?
A spike to review the bundle's design is about one to two days, and a working Laravel implementation is roughly three to five days for one engineer. That includes a migration, Eloquent model, code generator, redirect controller, and basic validation. Hardening with rate limiting, scheme allow-lists, and expiry semantics adds a little more time but remains cheaper than maintaining a dead dependency.
Weaver

How can I help you explore Laravel packages today?

Conversation history is not saved when not logged in.
Prompt
Add packages to context
No packages found.
shitoudev/permissionmanager
johannesclimacus/laravel-tui
hocvt/seotools
vitalybaev/sypexgeo
amphibee/themosis-ignition
gito-me/fast-excel
frankyso/laravel-ipaymu
geolize-studio/laravel-chile
boomerangui/chat
jinas/dhivatar
store-doc/laravel-storage-driver
plus-it/laravel-translation-manager
diephp/perhaps
diephp/telegraph
osmaviation/spreadsheet
microsoft/fluentui-system-icons
mmccook/php-json-canonicalization-scheme
middlewares/firewall
qubiqx/montapacking
nyoncode/laravel-package-console