berlioz/event-manager

This is a generally healthy, actively maintained package with a stable major release, five releases in the last 12 months, a non-archived organization-backed repository, a small dependency surface, and no install-time lifecycle scripts. The main concerns are a very small and concentrated recent contributor base, minimal repository popularity, no tests in either the artifact or repository, and no published security policy. The repository README explicitly identifies the project as a read-only split and directs contributions to the main framework repository, which provides context for the small repository footprint and single-repository maintainer activity. Overall, it appears reasonable to depend on, but adopters should account for limited visible independent maintenance capacity and testing evidence.

Latest v3.2.1

Packagist

78%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Package scaffolding

A README and changelog are present, and the repository uses GitHub Releases, but tests are absent from both the artifact and repository. For a small library this is a meaningful maintenance and verification gap.

Repo bus factor

One contributor made 100% of the 3 commits in the last 3 months, creating a concentrated maintenance risk. The organization-owned repository provides some potential handoff capacity, but no second active contributor is shown.

Repo commit activity

There were 3 commits in the last 3 months, showing recent activity, but all activity came from only one active maintainer.

Repo popularity

The repository has zero stars and forks and only two watchers. Popularity is supporting evidence rather than a verdict, but these counters provide little external validation.

Security policy

The repository has no SECURITY.md or other detected security policy, leaving vulnerability reporting and response expectations undocumented.