meita/laravel-zatca-einvoice

Release historydanger

The package has only two releases, both published within about 19 hours, followed by roughly 10 months without a newer release. This limited and stalled release history is a meaningful maintenance concern.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months; together with the long gap since the last release, this indicates likely abandonment or very slow maintenance.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but these values provide no external evidence of community adoption or backup.

Repo toolingcaution

Composer is used for the build, which is appropriate for a Laravel package, but no security scanning tools are configured. For an invoice and compliance integration, that is a transparency and maintenance gap.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling security issues in a package that generates and integrates business invoices.