Package Health/devgroup/yii2-graylog-target

devgroup/yii2-graylog-target

Usable but aging: the package has no releases in the last 12 months and the repo’s last push was in 2018. It’s maintained by a single person and has no security policy or CI workflow audit evidence, though the artifact includes readme/tests/changelog and a matching BSD-3-Clause license.

Latest 0.9.1

Packagist

58%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one maintainer has publish access, so the project has a very limited bus factor for review, releases, and responsiveness. This increases operational risk despite other packaging positives.

Release history

Releases are sparse (2 total) and there were 0 releases in the last 12 months, with the latest release dating back to 2016. That strongly suggests slow or stopped maintenance for this dependency line.

Repository archived

The repository is not archived, but the last push was about 7–8 years ago, which is consistent with abandonment risk over time. This lowers confidence that fixes will land quickly if something breaks.

Security policy

No security policy is present in the repository metadata, so there is no documented process for reporting vulnerabilities. This is a transparency gap, especially for an older, maintenance-light project.

Workflow audit

The workflow audit reports workflows_total = 0 and workflows_analyzed = 0, so there is no CI/workflow evidence to check pinning, permissions, or risky patterns. This lowers assurance for supply-chain hygiene.