Package Health/programinglive/sentry-resolve

programinglive/sentry-resolve

Maintenance has gone quiet after an unusually concentrated release period, and the repository has no recent commit activity. The package is well documented and tested, with clear ownership and licensing, but its single registry maintainer and lack of security scanning reduce confidence.

Latest v1.1.8

Packagist

60%

Total Score

Maintainer Stability

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one account has registry publish access, which is a resilience concern by itself. The repository is organization-owned, so this is a smaller concern than a lone individual-owned project would be.

Release history

The package published 22 releases in its first year, but all were concentrated in the last 12 months and the latest release was about nine months ago. This suggests an abrupt maintenance pause rather than a sustained cadence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the roughly nine-month gap since its last push. That materially raises abandonment risk.

Repo popularity

The repository has zero stars, forks, and watchers, so there is little visible community support or external review to compensate for the inactive maintainer activity.

Repo tooling

Composer is used as the build tool, but no security scanning tools were detected. The missing scanning is a hygiene gap, though it is less serious than the observed maintenance slowdown.

Vulnerabilities

We didn't find any vulnerabilities for this package.

Package versions

Maintainers

Programing Live

Direct Dependencies

Dependency	Last Release	Score
sentry/sdk Version ^4.0	—	—
symfony/console Version ^6.0\|^7.0	—	—
symfony/process Version ^6.0\|^7.0	—	—
vlucas/phpdotenv Version ^5.6	—	—
guzzlehttp/guzzle Version ^7.0	—	—