Weave Code
Laraveleasyattendance Laravel Package
easybdit/laraveleasyattendance
EasyAttendance is a Laravel package for simple attendance management. Track employee check-ins and check-outs, store daily attendance records, and query or report on attendance data through a clean, configurable integration built for Laravel apps with minimal setup.
Drop-in attendance, HR, and payroll core for any Laravel app — check-in/out, ZKTeco device sync, shifts, leave, salary generation.
Frequently asked questions about Laraveleasyattendance
- What is easybdit/laraveleasyattendance and what does it do?
- EasyAttendance is a Laravel package that provides a drop-in attendance, HR and payroll core for existing applications. It handles employee check-in and check-out, daily attendance records, shifts, leave, ZKTeco device sync and salary slip generation through Eloquent models, traits, migrations and a config-driven service provider. It is aimed at Laravel apps that need attendance tracking with minimal setup rather than a full standalone HR system.
- How do I install and configure EasyAttendance in a Laravel app?
- Install it with Composer, publish the package config and migrations, point the attendance.subject_model setting at your app's employee model, then run migrations. No queues, external services or special drivers are mentioned in the release notes, so the mechanical setup is low friction. The real integration gate is whether your domain matches the package's assumptions: a single subject model, date-only leave semantics, and one shift, designation and department hierarchy per employee.
- Which Laravel and PHP versions does Laraveleasyattendance support?
- The v2.3.1 release notes do not state a supported Laravel or PHP version matrix, and no dependency manifest or CI configuration is covered in the available context. Check the package's composer.json constraints and its CI matrix before committing, and treat any version claim as unverified until the maintainer confirms it. This is one of the open questions raised in the technical assessment.
- Can I use my own Employee model with EasyAttendance?
- Yes. The employee subject is resolved at runtime from the attendance.subject_model config value, so the package binds to whatever model your application provides instead of hard-coding one. The trade-off is an untyped boundary: the package cannot statically reason about the relations it calls, so Larastan and your IDE cannot validate them. The maintainers have documented this as an accepted design decision, not a defect.
- Does EasyAttendance sync with ZKTeco biometric devices?
- ZKTeco device sync is listed as a core feature in the package description, covering attendance pulled from ZKTeco biometric devices. The release notes do not describe the sync driver, protocol, scheduling or network requirements, so confirm those details against the source and your specific device models. No external service or queue dependency is mentioned, but verify how sync is triggered in production.
- Are the EasyAttendance migrations safe to run on an existing attendance schema?
- This is not confirmed. The available context does not state whether the migrations are additive, idempotent or destructive, which matters if you already have attendance tables. Run them against a copy of your schema first and check for table name collisions before touching production. Migration reversibility is explicitly listed as an open question for the maintainer.
- Does Laraveleasyattendance generate payroll and salary slips?
- Yes, payroll is part of the package's scope: it ships a SalarySlip model alongside the attendance and leave models, and the overview describes salary generation. The release notes do not cover tax rules, deductions, payslip formatting or payroll cycles, so review the source before relying on it for real payroll. Treat salary generation as a core to extend rather than a complete payroll product.
- How does leave day counting work in EasyAttendance?
- Leave::daysCount() calculates the difference between leave dates and casts the result to an integer, which implies date-only leave semantics with no half days. In v2.3.1 that cast was made explicit, described as a type-level formalization of behaviour that was already implicitly correct rather than a new computation. Confirm it returns identical values for all your inputs, especially any case where a fractional day could previously have carried through.
- Will Larastan or PHPStan report errors when using this package?
- Expect some static analysis noise. The v2.3.1 notes mention 16 remaining baselined findings, all tied to the runtime subject_model pattern, and any code you write through that boundary will inherit the same class of error. Larastan's relation validation for with() calls will not cover it, so plan baseline entries or typed wrappers in your own code.
- Is v2.3.1 a safe upgrade from 2.3.0 and is the package production ready?
- The 2.3.1 patch is described as developer experience and static analysis only, with no claimed runtime behaviour change and no breaking changes from 2.3.0. The diff is wide because docblocks were added across every model, which is semver-safe but can create merge conflicts in forks or local overrides. Nothing in the notes indicates what a 2.x to 3.x upgrade would involve, and the package's testing posture is not described, so assess production readiness against the source rather than the release notes alone.
Weaver
How can I help you explore Laravel packages today?