Package Health/nvn-m2labru/pact-im-sdk-php-php7.2

nvn-m2labru/pact-im-sdk-php-php7.2

This is a usable but very new package with solid basic packaging hygiene: it has an MIT license, a complete-looking 48-file tree, repository tests, Composer build tooling, no install lifecycle scripts, and no deprecation notice. However, the release history contains only one release from the assessment day, the repository has no commits or active maintainers in the preceding three months, has no security scanning or security policy, and the README does not mention the package despite the repository name matching it. These limitations create meaningful maturity, transparency, and continuity risk, although the repository is not archived and the zero activity is partly explained by the package's age.

Latest 1.0

Packagist

65%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Dependency profile

Six runtime dependencies, including PHP and required extensions, create a nontrivial compatibility surface for a small SDK, but the dependency set is explicit and not unusually large.

Release history

There is only one release and the package is 0 days old, so it has no demonstrated release continuity or maintenance history. Its very recent creation makes this an immaturity concern rather than evidence of abandonment.

Repo commit activity

The repository has zero commits and zero active maintainers in the last three months. Because the package is 0 days old, this is consistent with a new project but still leaves maintenance capacity unproven.

Repo popularity

The repository has zero stars, forks, and watchers. This is weak supporting evidence for maturity, though popularity alone is not decisive for a newly created package.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured, leaving a security-hygiene gap.