Weave Code
Url Tokenizer Bundle Laravel Package
gollumsf/url-tokenizer-bundle
A Symfony bundle for URL tokenization that integrates tokenizer functionality into your app, helping parse and split URLs into usable tokens for analysis, routing, or custom processing. Lightweight and easy to wire into existing Symfony projects.
gollumsf/url-tokenizer-bundle brings structured URL tokenization to Symfony applications. It registers the underlying tokenizer as a container service, letting you split URLs into discrete components—scheme, host, path, query, and fragment—without brittle string manipulation. Configuration lives in standard bundle YAML, so the tokenizer can be injected wherever routing, redirect handling, or link analysis is required.
- Autowired tokenizer service through Symfony DI
- Splits URLs into scheme, host, path, query, and fragment
- YAML configuration with sensible defaults
- Reusable, framework-agnostic tokenizer core
- Composer-installable with PSR-4 autoloading
Frequently asked questions about Url Tokenizer Bundle
- Is gollumsf/url-tokenizer-bundle a Laravel package or a Symfony bundle?
- It is a Symfony bundle. It ships a Symfony DI extension, configuration tree, and service definitions wired through Symfony's container, with no Laravel service provider, facade, or Laravel-format config file. Laravel's package discovery will not register it.
- Can I install gollumsf/url-tokenizer-bundle in a Laravel application?
- Composer can install it, but there is no Laravel integration. You would either pull symfony/dependency-injection and symfony/config into the app and hand-bootstrap the container, or extract the tokenizer core and wrap it in an Illuminate\Support\ServiceProvider. Both paths are bespoke work you own.
- Which Laravel versions are supported by gollumsf/url-tokenizer-bundle?
- None are declared. The package targets Symfony and does not ship Laravel service providers or constraints for the Laravel framework. Check its composer.json for Symfony and PHP constraints instead, since those are the only declared requirements.
- Is the GPL-3.0 license of gollumsf/url-tokenizer-bundle safe for a commercial Laravel product?
- GPL-3.0 is copyleft and can compel source disclosure of derivative works, so legal review is mandatory before shipping it in a proprietary distributed product. Internal SaaS use is more likely tolerable, but that is a counsel decision, not an engineering one. Do not land the code without written clarification.
- How do I create tamper-evident URLs in Laravel without this package?
- Use URL::signedRoute() for permanent signed URLs and URL::temporarySignedRoute() for time-limited links with built-in expiry. Validate incoming requests with the signed middleware or hasValidSignature(). This covers most unsubscribe, password reset, share link, and signed download use cases natively.
- What is the difference between URL tokenization and Laravel signed URLs?
- A URL tokenizer splits and inspects URLs into structured tokens for routing or analysis, while Laravel signed URLs add HMAC tamper-evidence and optional expiry to generated links. The package description does not clarify whether its tokens provide tamper-evidence, opacity, or both. Confirm the requirement before assuming it replaces signedRoute().
- How do I generate opaque or encrypted URL tokens in Laravel?
- Use Crypt::encryptString() and Crypt::decryptString() with an app-key-derived cipher key. Wrap the payload in a versioned envelope if you need future format changes. Hashids or Sqids are suitable when you only need obfuscated IDs rather than confidentiality.
- Is gollumsf/url-tokenizer-bundle actively maintained?
- It has a single maintainer, 1 star, and 0 dependents, so external validation is minimal. The listed last release date of 2026-08-28 post-dates the current date, which suggests a metadata anomaly, and should be verified against the actual repository tags. Treat release cadence as unproven until then.
- How do I integrate a Symfony bundle's services into Laravel's container?
- Laravel's container does not consume Symfony DI extensions or config trees. The realistic options are to boot a Symfony container alongside Laravel, which adds a large dependency footprint, or extract the tokenizer core into app/Support/UrlTokenizer and register it through your own service provider. Most teams choose extraction and thereby maintain a fork.
- What are the best alternatives to gollumsf/url-tokenizer-bundle for Laravel?
- Native Laravel primitives cover the common cases: URL::signedRoute() and URL::temporarySignedRoute() for signed links, Crypt for opaque payloads, and Hashids or Sqids for obfuscated IDs. Choose the package's token format only if you must interoperate with an existing Symfony service, and clear the GPL-3.0 license first.
Weaver
How can I help you explore Laravel packages today?