Package Health/puyu-pe/sipro-internal-api-clone-db

puyu-pe/sipro-internal-api-clone-db

The four-file package is clearly tied to its repository and has a stable 1.0.1 release. Organization backing and the absence of install scripts reduce, but do not remove, the maintenance uncertainty.

Latest 1.0.1

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has existed for 179 days but has only one release, with no demonstrated release cadence. That limits evidence of maturity and ongoing maintenance.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, despite the package being 179 days old. This is the strongest abandonment concern in the available evidence.

Repo popularity

The repository has 0 stars, forks, and watchers, so there is little public evidence of adoption or community support. Its internal-looking scope and organization backing make this less significant than it would be for a general-purpose library.

Repo tooling

Composer is used for the build, but no security scanning tool was detected. That is a modest process gap, not evidence that the package is unsafe or abandoned on its own.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This is a minor transparency gap given the package's small, internal-looking scope.