Package Health/aws/aws-sdk-php-v3-bridge

aws/aws-sdk-php-v3-bridge

The project has gone more than three years without a registry release, and recent repository commits are absent. AWS organization backing, repository tests, licensing, and a release note provide useful transparency, while workflow references remain unpinned.

Latest 0.4.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

100

Health Score Breakdown

Release history

The latest release was over three years ago, with no releases in the last 12 months and only five releases across roughly 11 years. This indicates a slow or possibly dormant release process, although the repository remains active enough to avoid treating it as abandoned outright.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the long release interval, this is a meaningful maintenance concern, though it does not prove abandonment by itself.

Repo issue activity

Only one issue is open and there have been no new or closed issues or pull requests in the last month. This is consistent with a quiet project but provides little evidence of active maintenance.

Repo tooling

Composer is used as the build tool, but no security scanning tool was detected. The missing scanning is a hygiene gap rather than a standalone reason to reject the release.

Version stability

Version 0.4.0 is a non-prerelease release, so consumers are not relying on an explicitly experimental build. The sub-1.0 version still leaves more compatibility uncertainty than a stable major release.