Package Health/lajosbencz/stream-parse-sql

lajosbencz/stream-parse-sql

Tests, a README, and clear licensing provide a workable baseline. The lack of security tooling and the very small public footprint add friction for long-term adoption.

Latest v0.1.1

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only two releases, both in January 2020, and no releases in roughly 6 years and 8 months. That long release gap is strong evidence of abandonment risk.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the old last push, this indicates that maintenance has stopped rather than merely slowed.

Project backing

The package and repository are owned by the same individual account, providing direct ownership alignment. There is no organizational backing shown to compensate for the single-person maintenance risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides little supporting evidence of active use or community resilience.

Repo tooling

Composer is used for the build, but no security scanning tools are present. The missing scanning is a modest hygiene gap, not evidence that the package is unsafe by itself.