ruwork/aws-bundle

The MIT license and two runtime dependencies keep the package straightforward to inspect and integrate. Ongoing support is difficult to verify because the repository has no security scanning and very little visible community activity.

Latest 0.13.5

Packagist

39%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was about seven years and eight months ago, and there have been no releases in the last 12 months. Although 30 historical releases show earlier activity, the prolonged release gap materially raises abandonment risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed recent maintenance.

Repo popularity

The repository has zero stars and forks and only four watchers, providing little evidence of an active user or contributor community. Popularity is supporting evidence, but this reinforces the maintenance concern.

Repo tooling

Composer is used as the build tool, which is appropriate for the package, but no security scanning tools are configured. This leaves an avoidable verification gap for a package that has otherwise been inactive for years.

Security policy

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less severe than the lack of recent maintenance.