sergios/bug-report

The project has no security policy or automated security scanning, while seven pull requests remain open with no recent merges. The MIT license, matching repository, and stable release format help, but do not offset the maintenance risk.

Latest 2.5

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in October 2019, and there have been no releases in the last 12 months. This long release gap is a meaningful abandonment concern, despite the package having four releases overall.

Repo issue activity

The repository has seven open pull requests but no new or merged pull requests in the last month, suggesting changes are not being actively integrated. There are no open issues, which is mildly reassuring but does not offset the stalled contribution activity.

Repo tooling

Composer is used for the build, but no security-scanning tools are configured. The absence of scanning reduces maintenance assurance, although it is not evidence of a security incident by itself.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency and maintenance gap for a package that handles application and user-reporting workflows.