bacarin/bacatools

bacarin/bacatools 1.0.0 appears usable and reasonably transparent, with an MIT license, a coherent 19-file repository, documented functionality, and tests covering the source code. However, this is a brand-new release with no demonstrated release or maintenance history, no repository security policy or security scanning, and no adoption or contributor track record; the single-user ownership also provides limited evidence of long-term maintenance capacity. It is not deprecated or archived and has no install-time lifecycle scripts, but adoption should be accompanied by monitoring for follow-up releases and maintenance activity.

Latest 1.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

A single registry maintainer limits visible publishing redundancy, although the linked user-owned repository provides direct project ownership context; this remains a modest maintenance-capacity concern rather than a severe risk.

Project backing

The repository is owned by a user rather than an organization, providing direct ownership but limited evidence of institutional backing or maintainer redundancy.

Release history

Only one release exists and the package is 0 days old, so there is no observed history demonstrating sustained maintenance, compatibility management, or dependable release practices.

Repo issue activity

There are no issues or pull requests and no activity in the last month; because the repository is newly created, this does not by itself demonstrate neglect, but it leaves maintenance responsiveness untested.

Repo popularity

The repository has 0 stars, forks, and watchers. This is weak supporting evidence, but the package's 0-day age substantially explains the absence of adoption data.