pessek/event_manager

Its five-file artifact and absent security policy provide little transparency for a plugin consumers must integrate. Stable versioning and no install-time scripts reduce operational risk, but they do not offset the weak maintenance evidence.

Latest 12.4

Packagist

39%

Total Score

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published about five years ago, with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended to manage application events.

Package file tree

The package and repository each contain only five files, with no evident documentation or test structure. That small footprint may be intentional, but it leaves limited evidence of mature project practices.

Package scaffolding

The artifact has no README, tests, or changelog; absent tests and changelogs are normal for published artifacts, but the missing README reduces consumer transparency for an integration plugin.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive for a small package, but these counters provide no supporting evidence against the stale release history.

Security policy

The repository has no security policy. This is not severe on its own, but it weakens transparency for a package that manages event and subscription functionality.