yummuu/workflower

Risky to adopt: the package has seen no release or commit activity for about four years and five months. It is not deprecated or archived, and it includes tests, a readable source tree, and an MIT declaration, but the inactive solo project offers little evidence of ongoing maintenance.

Latest 1.0.3

Packagist

43%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases, with the latest published about four years and five months ago and none in the last 12 months. This is strong evidence of abandonment risk for a workflow engine.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this lack of current maintenance.

Repo popularity

The repository has zero stars and forks and only one watcher, offering little supporting evidence of an active user or contributor community. Popularity is secondary, but it provides no counterweight to the maintenance gap.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That leaves fewer visible safeguards for ongoing maintenance, although the absence of workflows means there is no workflow-specific risk to weigh.

Security policy

No security policy is present, reducing transparency for reporting vulnerabilities in a package that processes workflow definitions. This is a hygiene concern rather than evidence that the package is unsafe.