Package Health/saywebsolutions/lets-blog

saywebsolutions/lets-blog

Risky to adopt: this package has had no release since April 2018 and no repository commits in the last three months, with very little community activity. Clear licensing, documentation, and a matching source repository help, but the long-standing inactivity makes maintenance and compatibility a serious concern.

Latest 0.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, published in April 2018, with no releases in the last 12 months. This is strong evidence that the package is no longer actively maintained.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the last registry release being in April 2018, this indicates a substantial abandonment risk.

Repo issue activity

There are no open issues or pull requests and no issue or pull-request activity in the last month. While a quiet project can be stable, this provides no evidence of ongoing community maintenance alongside the inactive release history.

Repo popularity

The repository has one star, no forks, and no watchers. Popularity is only supporting evidence, but these very low adoption indicators provide little external evidence of maturity or support.

Repo tooling

Composer is used as the build tool, but no security scanning tools are present. The missing scanning is a transparency and maintenance gap, though it is not severe enough to make the package unfit on its own.