rehmanafzal/dbmanager

Documentation and packaging are clear, with a declared MIT license and no install-time scripts. Maintenance evidence is thin: this is the only release and the repository recorded no commits or active maintainers in the last three months; security tooling and a security policy are also absent.

Latest v1.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Project backing

The repository is owned by an individual user rather than an organization. That is not inherently unhealthy, but it provides less visible backing for a package whose maintenance evidence is already limited.

Release history

The package is 166 days old with only one release, so there is little release history to demonstrate sustained maintenance. Its recent origin partly explains the limited history, keeping this a caution rather than a severe abandonment signal.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. With only one release, this leaves ongoing maintenance unproven and is the main reason for the caveat.

Repo tooling

Composer is used as the build tool, but no security scanning tools were detected. That is a meaningful repository hygiene gap for a package that exposes database-management functionality.

Security policy

The repository has no security policy. This weakens vulnerability-reporting transparency, although it is not evidence that the release is unsafe by itself.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

No maintainer information available.

Direct Dependencies

Dependency	Last Release	Score
illuminate/routing Version ^9.0\|^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/support Version ^9.0\|^10.0\|^11.0\|^12.0\|^13.0	—	—
illuminate/database Version ^9.0\|^10.0\|^11.0\|^12.0\|^13.0	—	—