elazar/flystream

Documentation and project structure are strong, with tests, a changelog, a matching repository, and an MIT license. Maintenance appears to be slowing, and all four workflow actions are unpinned, so pinning this version deserves care.

Latest 1.4.0

Packagist

67%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 11 releases over roughly five years, but none in the last 12 months; the long release gap lowers confidence in ongoing maintenance without indicating abandonment alone.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with no registry releases in the last 12 months, this is evidence of slowing maintenance and raises update-risk concerns.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected; this is a modest repository hygiene gap rather than evidence of abandonment.

Security policy

The repository has no security policy, which reduces transparency for reporting vulnerabilities, though this alone does not make the release unfit to use.

Workflow audit

The single workflow was fully analyzed with no dangerous triggers or audit findings, but all four action references are unpinned, leaving avoidable dependency-integrity risk in CI.