brapastor/container

Risky to depend on: this package has had only one release, published about 9 years ago, with no evidence of ongoing maintenance. It is not deprecated or archived and includes tests, but its age and lack of consumer documentation make it a poor production dependency.

Latest 0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, with no releases in the past 9 years. That strongly indicates abandonment risk, despite the package remaining available on the registry.

Package scaffolding

The artifact and repository include tests, which is a positive quality signal, but the package has no README. For a library consumers must integrate, missing usage documentation is a meaningful transparency and usability gap.

Project backing

The registry namespace is brapastor while the linked repository is owned by a different user account, grekodev. The repository is user-owned rather than organization-backed, so this creates some ownership transparency concern.

Repo popularity

The repository has zero stars and forks and only one watcher. This is supporting evidence of limited adoption, though popularity alone is not decisive for a small package.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security scanning tooling is present. The absence of scanning is a modest transparency gap rather than evidence of unsafe behavior.