- What is andrey-helldar/blacklist-core used for?
- It provides the foundational blacklist management layer for PHP and Laravel applications. The core includes reusable rules, storage abstractions, and validation helpers for blocking unwanted emails, domains, IPs, or custom values. It is intended to be shared by blacklist server and client implementations rather than being a full end-user application.
- How do I install andrey-helldar/blacklist-core with Composer?
- Install it as a Composer dependency with composer require andrey-helldar/blacklist-core. In a Laravel application, check the repository for any service provider or configuration publishing steps. Because it is a core package, you may also receive it indirectly through a blacklist server or client package that depends on it.
- Does blacklist-core support Laravel 10 or Laravel 11?
- The package is built for PHP and Laravel applications, but exact Laravel version support depends on the release. Check the composer.json constraints and the repository README for the supported Laravel and PHP versions before installing. If you need an older or newer Laravel release, verify compatibility through Composer or the package maintainer.
- Can blacklist-core block emails, domains, IPs, and custom values?
- Yes, the package is described as providing reusable blacklist rules and validation helpers for emails, domains, IPs, or custom values. The core is designed to be generic so applications can define the values they want to reject. You should review the available rule and validator classes in the repository for the exact implementation details.
- How does blacklist-core store blacklist entries?
- The core provides storage foundations for blacklist data, but the exact storage mechanism depends on the implementation and configuration in your application. Review the repository for the available storage classes or contracts and how to extend them. For production, choose a storage approach that matches your expected lookup volume and caching strategy.
- Is blacklist-core a complete blacklist server?
- No, the package is described as the core for a blacklist server and client, not the complete server itself. It supplies foundational rules, storage, and validation helpers that other packages or applications can build on. You will typically use it as part of a larger blacklist implementation or as a dependency of the server or client package.
- How do I validate an email or IP against a blacklist in Laravel?
- Use the validation helpers and blacklist rules provided by the core, integrated into your Laravel validation flow. The package is designed to make it easier to define reusable rules for emails, domains, IPs, and custom values. Check the repository for the exact rule names and examples before wiring them into form requests or validators.
- Can I use andrey-helldar/blacklist-core without Laravel?
- The package is described for PHP and Laravel applications, so the core classes may be usable in plain PHP projects. However, Laravel-specific integration points, such as service providers or validation bridges, may not apply outside Laravel. Check the repository for framework dependencies and usage examples before using it in a non-Laravel project.
- How should I test blacklist rules in a Laravel application?
- Test your blacklist rules with the same Laravel testing tools you use for other validation and service classes. Use unit tests for reusable rule logic and feature tests for the application flows that reject blacklisted emails, domains, IPs, or custom values. Keep test data isolated so blacklist storage does not leak between test cases.
- What are alternatives to andrey-helldar/blacklist-core?
- Alternatives depend on whether you need a full blacklist server, a Laravel validation rule, or a storage layer for blocked values. You can compare other Laravel blacklist or disposable-email validation packages, or implement custom rules with Laravel's validator. Evaluate the alternatives for supported value types, storage options, Laravel compatibility, and maintenance activity.