arillo/logslackwriter

Its small, focused artifact has a clear README, a stable version, and no install-time scripts. However, the project shows no releases or repository commits since December 2017, with no recent issue activity and no security scanning, making abandonment a serious concern.

Latest 1.0.1

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases were published, with the latest on December 18, 2017; there have been no releases in more than eight years. This is strong evidence of abandonment for a dependency that may need compatibility updates.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the unchanged release history and indicating no current maintenance capacity.

Repo issue activity

There were no new or closed issues or pull requests in the last month, and one issue remains open. This reinforces the lack of visible ongoing maintenance, though issue volume is limited for a small package.

Repo popularity

The repository has 4 stars, 0 forks, and 2 watchers, providing little evidence of a broad user or contributor base. Popularity is supporting evidence rather than a verdict, but it offers no compensating maintenance signal here.

Repo tooling

Composer is used for the build, which fits the package ecosystem, but no security scanning tools are configured. This is a modest transparency and maintenance gap, not evidence of malicious behavior.