Package Health/apigatewaycl/apigateway-api-client

apigatewaycl/apigateway-api-client

The project has stopped committing recently, and every GitHub Actions dependency is unpinned. It remains well documented, tested, licensed, and backed by an organization, but its slow release history and absent security policy add maintenance uncertainty.

Latest 3.0.0

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases over about 32 months, with one release in the last 12 months and a median interval of about 14 months; this indicates a slow maintenance cadence.

Repo commit activity

There were zero commits and zero active maintainers in the last three months, a concrete sign that maintenance has recently stalled.

Repo tooling

Composer is used for builds, but no security scanning tools are present in the repository, leaving a security-hygiene gap.

Security policy

The repository has no security policy, reducing transparency about how users should report vulnerabilities and how maintainers handle them.

Workflow audit

Both workflows were analyzed successfully with no dangerous triggers, untrusted checkouts, or audit findings. However, all 7 action references are unpinned, which weakens build reproducibility and supply-chain hygiene.