gvera/response-types

The small codebase includes tests, an MIT declaration, and no install scripts, which reduces adoption friction. It has no README or security policy, and its minimal public traction offers little additional confidence.

Latest 1.1

Packagist

42%

Total Score

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, both in June 2021, with no release in roughly five years. That is strong evidence of abandonment risk despite the package not being deprecated.

Package scaffolding

The package and repository contain tests, which is useful evidence of basic validation. The missing README reduces consumer transparency for a library, while the absent changelog is normal because release notes for this version are not provided.

Repo package mention

The repository name does not match the package name, and no README package mention was collected. That weakens confidence that the linked repository is the package's clearly identified home.

Repo popularity

The repository has zero stars and forks and one watcher. Popularity is not required for a healthy small package, but these counters provide no supporting evidence of active community use.

Repo tooling

Composer is used as the build tool, but no security-scanning tooling is reported. For this small package that is a minor transparency gap rather than a standalone severe risk.