optimus/architect

The package is clearly documented, licensed, and backed by repository tests, with a small dependency surface. Its limited security tooling and inactive issue handling add some maintenance uncertainty.

Latest 2.0.5

Packagist

61%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

There have been zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is the strongest abandonment concern.

Project backing

The repository is owned by an individual rather than an organization, so the small maintainer and contributor footprint provides limited visible backing for continued maintenance.

Release history

The package has existed since 2015 with 11 releases, but it has had no release in roughly 20 months. That is meaningful evidence of slowing maintenance, though the stable 2.0.5 release remains established.

Repo issue activity

There are three open issues and four open pull requests, but none were opened or closed in the last month and no pull requests were merged. This indicates unresolved maintenance demand.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap rather than evidence that the package is unsafe.