gvera/core-services

The package has a small dependency footprint, tests, and an MIT declaration. Its lack of recent activity and minimal public footprint make future fixes uncertain; pin this version only if its narrow functionality is already validated.

Latest 1.2

Packagist

43%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published nearly five years ago, and there have been no releases in the last 12 months. This is strong evidence of abandonment risk despite the package having three releases overall.

Repo commit activity

There were no commits and no active maintainers in the last three months, reinforcing the release-history evidence that maintenance has stopped.

Package scaffolding

The artifact and repository include tests, and the exact version has a GitHub release. The missing README and changelog reduce transparency for a library consumers must integrate, although the tests provide some compensation.

Project backing

The repository is owned by an individual account rather than an organization. That is not inherently unhealthy, but it offers no visible organizational backing to offset the inactive history.

Repo package mention

The repository name does not match the package name, and the collected README reference is unknown. The mismatch makes package ownership less transparent, though it could still reflect a sub-package naming arrangement.