flycorp/bradesco

The README gives practical Laravel and configuration guidance, and the MIT license with three runtime dependencies keeps adoption straightforward. There is no security policy or repository scanning, leaving maintenance and security transparency thin.

Latest 0.0.4

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in the last 12 months, and its latest release was nearly three years ago; four releases clustered at the start suggest abandoned maintenance rather than an established cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and leaving no evidence of ongoing maintenance.

Maintainers

Only one registry account can publish the package, creating a thin publishing base; the linked repository is user-owned rather than organization-owned, so there is no provided backing signal to offset that concentration.

Repo popularity

The repository has zero stars and forks and one watcher. This provides little external validation, but low popularity alone is not evidence of abandonment.

Repo tooling

Composer is used as the build tool, but no security scanning tools are configured; the missing scanning is a modest transparency gap rather than evidence of unsafe behavior.