jbzoo-cck/jbzoo

Clear licensing, tests, and release notes make the project easier to maintain and integrate. However, there have been no registry releases in the last 12 months and no commits in the last 3 months, so maintenance appears paused.

Latest 4.50.3

Packagist

62%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 24 releases since July 2020, but it has had no releases in the last 12 months despite version 4.50.3 being stable. That points to a meaningful maintenance pause.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. Combined with no registry releases in the last 12 months, this is evidence of paused maintenance.

Repo issue activity

There were 18 open issues and 5 open pull requests, but no new or closed issues and no merged pull requests in the last month. This suggests limited recent project response.

Repo tooling

The repository uses Make and Composer for builds, showing basic build structure, but no security scanning tools were detected. The missing scanning is a hygiene limitation rather than a severe dependency risk.

Security policy

The repository has no security policy. For a substantial Joomla extension with a large code tree, this reduces transparency about vulnerability reporting and maintenance expectations.