Package Health/brianalzatedeveloper/apismsrest

brianalzatedeveloper/apismsrest

The package has a clear MIT license, a small dependency footprint, tests, and a repository that matches its name. Its documentation is still an untouched Bitbucket template, and there is no security policy or scanning; pinning this version would leave little evidence of ongoing support.

Latest v1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This is the only release, published about 6 years and 11 months ago, with no releases in the last 12 months. That is strong evidence of abandonment risk, though the package is not marked deprecated.

Repo commit activity

The repository has recorded no commits and no active maintainers in the last 3 months, consistent with the release history showing no activity since October 2019. No newer maintenance evidence compensates for this gap.

Package scaffolding

The artifact includes tests and a README, but the README is still a generic Bitbucket setup template rather than usage documentation for this package. The missing changelog is normal packaging practice and is not a concern by itself.

Repo popularity

The repository has zero stars and forks and only one watcher, providing little supporting evidence of community use or review. Popularity is only supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo tooling

Composer is used for builds, but no security-scanning tooling is present. This is a modest hygiene gap rather than a severe risk, especially because the dependency profile is small.