Package Health/everyworkflow/remote-bundle

everyworkflow/remote-bundle

The codebase is small, focused, and has a clear MIT license with limited runtime dependencies. It lacks tests, a README, a security policy, and security scanning, while the organization-backed project provides some ownership context. These safeguards do not compensate for the absence of activity since the initial release.

Latest v0.1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only one release, published about four years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

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 maintenance.

Package scaffolding

The published artifact has no README, tests, or changelog, and the repository also reports no tests or changelog. Although tests and changelogs are not expected in the artifact, the missing README and repository quality evidence reduce transparency.

Repo popularity

The repository has zero stars and one fork, showing little community adoption or visible validation. Popularity is supporting evidence only, so this modestly reinforces rather than drives the abandonment concern.

Repo tooling

Composer build tooling is present, but no security scanning tools are reported. That limits automated detection coverage for a package with no other compensating security process shown.