mirushaki/flowplayer

The package is compact, clearly licensed, and its repository matches the package, supporting straightforward use. Its simple dependency profile and lack of install-time scripts reduce adoption complexity, but provide little evidence of broader project maturity.

Latest v1.0.1

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both published in May 2019, with no release in more than seven years. This is strong evidence of abandonment risk despite the stable version.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Combined with the old last push, this materially increases abandonment risk.

Project backing

The package and repository are owned by the same individual account, so the source relationship is clear. There is no organization backing shown to provide additional continuity if that maintainer stops working on it.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. This is a modest transparency and maintenance gap rather than proof of unsafe code.

Security policy

The repository has no security policy. For a small, inactive package this leaves no documented route for reporting or handling vulnerabilities.