area17/edge-flush

All five workflow actions are unpinned, and the repository has no automated security scanning despite having a security policy. The package is licensed, documented, correctly linked to its organization, and not deprecated or archived.

Latest v2.0.7

Packagist

57%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release for more than 3 years, despite 64 releases overall; this is a substantial maintenance concern for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last 3 months, reinforcing the concern raised by the lack of releases.

Repo popularity

The repository has modest usage indicators with 9 stars and 3 forks; this is limited supporting evidence but not a health problem by itself.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected; this is a hygiene gap rather than evidence that the package is unsafe.

Workflow audit

Both workflows were fully analyzed with no dangerous sinks or audit findings, but all 5 action references are unpinned, leaving avoidable workflow supply-chain exposure.