jooservices/exceptions

This release appears well-scaffolded and transparent, with an MIT license, substantial documentation, tests, a changelog, matching repository, security policy, automated security tooling, and active repository work under organization ownership. However, it is only 5 days old with a single release, and all recorded commits in the last 3 months come from one contributor, so long-term maintenance and project maturity remain unproven. The package is usable as a dependency, but adoption should account for its very limited release history and concentrated development activity.

Latest v4.0.0

Packagist

68%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Lifecycle scripts

The package defines post-install-cmd and post-update-cmd scripts. Install-time scripts increase dependency integration sensitivity, although this signal alone does not establish abandonment or poor maintenance.

Release history

The package is only 5 days old and has one release, so there is no demonstrated history of sustained maintenance or release stability.

Repo bus factor

One contributor accounts for 100% of commits in the last 3 months, creating a concentrated maintenance dependency. Organization ownership provides some ability to hand off maintenance, but no second active contributor is shown by this signal.

Repo commit activity

Only one commit and one active maintainer were recorded over the last 3 months. Recent pull-request activity is encouraging, but the direct commit history remains too thin to demonstrate sustained maintenance.

Token permissions

Six workflows declare read-only permissions, but four declare top-level write permissions and one lacks top-level permissions. This is a workflow-hardening gap, though it is mitigated by the absence of dangerous workflow patterns.