micros/asobancaria

Usable with caveats: the package is clearly licensed, documented, lightweight, and not deprecated, but it has had only one release and no commits for about two years. Its single-maintainer project also lacks security policy and automated security scanning, so long-term support is uncertain.

Latest 0.0.1

Packagist

55%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one registry account has publishing access. This is not itself evidence of poor maintenance, but it leaves limited visible publishing redundancy when combined with the inactive repository.

Project backing

The registry namespace and repository owner match, but the owner is an individual account rather than an organization. This supports package identity while providing limited evidence of institutional backing.

Release history

This package has only one release, first published about two years ago, with no releases in the last 12 months. That leaves limited evidence of sustained maintenance and release discipline.

Repo commit activity

There were no commits and no active maintainers in the last three months, a strong indication that maintenance has paused since the initial release.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. For a small library this is a transparency and assurance gap, though it is not evidence of malicious behavior.