andriichuk/laravel-billing

Release historycaution

The package is only 0 days old and has four releases in roughly 19 hours, so there is not yet enough history to demonstrate durable maintenance or release discipline.

Repo commit activitycaution

The repository reports zero commits and zero active maintainers in the last three months, but the package is newly published and only 0 days old, so this is weak evidence of abandonment rather than a severe maintenance failure.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools are configured. That is a transparency and hygiene gap for billing software, though it does not by itself make the release unfit.

Security policycaution

The repository has no security policy, leaving no documented reporting process for security issues. This lowers transparency but is not independently severe for a brand-new package.

Version stabilitycaution

Version 0.2.2 is not a stable major release, and the README identifies the package as pre-1.0 while its contracts are still being validated. That is expected for an early project but increases compatibility risk.