tuxudo/jamf

The stable release has clear documentation and release notes. The MIT declaration and matching repository improve transparency, but this is not a strong choice for a dependency that needs active upstream support.

Latest v1.8

Packagist

55%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no registry release in about three and a half years, with zero releases in the last 12 months. Its nine releases and roughly 96-day median interval show prior activity, but the current gap raises maintenance risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers during the last three months. Combined with the older last push, this leaves little evidence of current maintenance capacity.

Project backing

The package and repository are owned by the same individual account rather than an organization. That is consistent ownership, but it also indicates a relatively thin backing structure for long-term maintenance.

Repo issue activity

There were no new or closed issues or pull requests in the last month, while two issues and one pull request remain open. This indicates limited recent project activity, though the small backlog is not severe by itself.

Repo tooling

The project uses Composer for builds, which is appropriate for a PHP package. No security scanning tooling was detected, leaving a modest transparency and maintenance-hygiene gap.