samuelcsantos/laravel-boleto

Release historydanger

Only two releases were published, both about two years and eight months ago, with no releases in the last 12 months. This is strong evidence of abandonment risk despite the repository remaining available.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old release history, this indicates maintenance has effectively stopped.

Repo issue activitycaution

There were no new or merged pull requests and no issue activity in the last month. This provides no evidence of ongoing project attention, although some counts are unknown.

Repo popularitycaution

The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but this offers no community-maintenance signal to offset the lack of recent activity.

Security policycaution

The repository has no security policy and no security-scanning tools. This is a modest transparency and maintenance gap for a package that handles financial document generation and related integrations.