pluswerk/comments

Risky to adopt for a new project: the release is usable and transparently tied to its organization-owned repository, but maintenance appears to have stopped about six years ago. The lack of tests and security policy adds concern for a user-facing extension.

Latest 1.2.1

Packagist

45%

Total Score

Maintainer Stability

100

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in about six years, with zero releases in the last 12 months; this is strong evidence of abandonment risk despite four early releases.

Package scaffolding

The package includes a readable README and has a GitHub release for this version, while the absence of tests and a changelog is normal for published artifacts; repository-level test coverage is nevertheless not shown.

Repo popularity

The repository has zero stars and forks and only two watchers, indicating limited visible adoption; popularity is supporting evidence, so this reinforces rather than determines the maintenance concern.

Repo tooling

Composer is used for builds, but no security scanning tools are reported; the missing scanning is a transparency and maintenance gap, though it is not evidence that the package is malicious.

Repository archived

The linked repository is not archived, which is a positive signal, but its last push was about six years ago and does not offset the very stale release history.