- How do I install Calendr in a Laravel application?
- Install it with Composer using composer require yohang/calendr. It is not a Laravel package, so you normally add a thin service provider or bind a CalendarService interface rather than expecting auto-discovery. Because the registry reports Repository: unknown, verify the package source and release integrity before production use.
- Does Calendr support Laravel 11 and Laravel 12?
- Calendr does not declare Laravel version support because it is framework-agnostic. In practice, Laravel 11 and 12 compatibility depends on its PHP constraint and your adapter; the evaluation treats PHP 8.2+ as aligned with that baseline. Confirm the actual Composer requirement before installing.
- Is Calendr a Laravel package or a framework-agnostic PHP library?
- Calendr is a framework-agnostic, object-oriented PHP domain library, not a Laravel package. That is useful because it can sit behind an application-level port and avoid coupling controllers or models to calendar internals. You will need to write the Laravel adapter yourself.
- How should I configure timezones and DST when using Calendr with Laravel?
- The overview does not specify whether Calendr stores UTC with zone rendering or floating local time. Centralize timezone configuration in Laravel and normalize dates at the adapter boundary. Test DST transitions, ambiguous local times, and non-existent local times explicitly.
- Does Calendr support recurring events and RFC 5545 RRULE?
- The overview describes querying events intersecting periods and flexible event collections, but it does not confirm RFC 5545 RRULE support. Do not assume full recurrence expansion; verify whether it handles recurrence rules, exceptions, and an infinite-series guard. If you need standards-based recurrence, validate that before committing.
- How do I integrate Calendr with Carbon and Eloquent models?
- There is no built-in Carbon or Eloquent bridge described. Build a bidirectional adapter between DateTimeImmutable or Carbon and Calendr's value objects, and add custom casts so persisted events round-trip without drift. Keep all conversion at the port boundary and pin a JSON date and offset format.
- How should I test a Calendr integration in Laravel?
- Test your adapter and boundary behavior, not just library calls: Carbon and DateTimeImmutable conversion, Eloquent casts, period intersections, and timezone normalization. Add cases for DST transitions, month and year boundaries, and recurrence limits. Until provenance is verified, do not rely on upstream tests alone.
- What are the production risks of using Calendr?
- The main production risks are unverified provenance because the repository is unknown, maintainer concentration, and silent correctness bugs in calendar logic. DST transitions, ambiguous local times, recurrence expansion, and ISO week numbering need explicit tests. Gate adoption on source verification, a security contact, reproducible builds, and bounded recurrence checks.
- What alternatives to Calendr exist for Laravel scheduling?
- For simple date ranges, Carbon and DatePeriod may be enough. For RFC 5545 recurrence, evaluate Recurr or rlanvin/php-rrule; for full scheduling, compare Laravel-oriented calendar packages. Calendr makes sense only if its object-oriented period and event model and framework independence justify writing an adapter.
- How is Calendr maintained and can I verify its repository and security?
- The technical evaluation reports a recent release on 2025-12-02, which suggests some liveness, but 467 stars and a low opportunity score point to niche momentum and likely one primary maintainer. Repository: unknown means you cannot currently verify CI, release signers, or a security policy. Treat provenance as an adoption gate and keep Calendr behind an interface so it can be swapped.