Package Health/bricks-framework/eventizr

bricks-framework/eventizr

The codebase is small and has no tests, limiting evidence for safe changes. Its license is explicit and install scripts are absent, but the lone release and inactive repository leave adoption exposed.

Latest 0.1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

This package has only one release, published over five years ago, with no releases in the last 12 months. That provides little evidence of ongoing maintenance or release responsiveness.

Repo commit activity

There were no commits and no active maintainers in the last three months. Given that the last push was over five years ago, this is strong evidence that maintenance has stopped.

Package scaffolding

The published artifact has no README, tests, or changelog, while the repository does contain a README. Missing tests reduce maintenance confidence, but absent tests and changelogs are not expected in every published artifact.

Repo package mention

The repository name matches the package, which supports the linkage, but its README does not mention the package. That weakens repository-to-package transparency slightly without proving the repository is unrelated.

Repo tooling

Composer is used for builds, providing ordinary project tooling, but no security-scanning tools are configured. The missing scanning is a modest transparency and hygiene gap rather than a standalone adoption blocker.