abmmhasan/bucket

This release appears usable and generally healthy: it is actively released, non-prerelease, not deprecated, backed by a current non-archived repository, and has a permissive MIT license, security policy, dependency scanning, and no install-time lifecycle scripts. The repository also has substantial documentation, CI/security tooling, and tests even though tests are not packaged. The main concerns are that all recent commits come from one contributor and the linked repository neither matches the package name nor mentions the package in its README, which weakens ownership transparency; the workflow also lacks an explicit top-level token-permissions declaration. Overall, the maintenance evidence is positive, but dependency adoption should account for the concentrated maintainer base and repository identity mismatch.

Latest 5.2.0Packagist

Health Score Breakdown

Maintainerscaution

Only one account has registry publish access; this is a mild transparency concern, although the organization-owned repository provides some project backing.

Repo bus factorcaution

All 15 recent commits were made by one contributor, creating a meaningful continuity and abandonment risk; organization backing partly mitigates this but does not remove the concentration.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, weakening confidence that the linked repository directly belongs to this release rather than being a related or reused project repository.

Token permissionscaution

The workflow lacks a top-level permissions declaration, leaving token permissions less explicit than preferred, although it declares no top-level write permissions.

View all 19 health checks

Vulnerabilities

We didn't find any vulnerabilities for this package.

Maintainers

abmmhasan