Package Health/myparcelcom/integration-commons

myparcelcom/integration-commons

This release has strong evidence of a real, maintained project: it has a five-year release history with 12 releases in the last 12 months, stable versioning, comprehensive source and test files, an Apache-2.0 license, no install-time lifecycle scripts, organization backing, and a repository that is not archived. However, Packagist marks this package as abandoned and provides the replacement `myparcelcom/marketplace-commons`, which is a major adoption risk even though the latest release and repository activity are recent. Commit activity shows no active maintainers in the last three months, and the repository lacks a security policy and explicit workflow token permissions. Prefer the replacement package for new dependencies unless compatibility requires this exact package.

Latest v4.0.14

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Registry deprecation

Packagist marks the package as abandoned and names `myparcelcom/marketplace-commons` as its replacement. This is a severe dependency risk because consumers may be relying on a package that has been superseded, despite recent releases elsewhere in the evidence.

Repo commit activity

The repository reports zero commits and zero active maintainers in the last three months. That suggests a thin or currently inactive development cadence, although the recent push and two merged pull requests provide some compensating evidence.

Repo package mention

The repository name does not match the package name and its README does not mention the package. This creates transparency about package-to-source ownership, although the organization backing and matching marketplace-commons context provide partial compensation.

Repo popularity

The repository has zero stars and forks and only two watchers, so it has little public adoption evidence. Popularity is supporting evidence only, and the organization backing, tests, and release cadence provide more relevant health evidence.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. The absence is a hygiene gap rather than evidence of an unsafe release.