wcmf/wcmf-default-app

The source repository is present, unarchived, and matches the package, with tests, a README, release notes, and a clear MIT license. Maintenance capacity is uncertain because no release has appeared for about 8 years, recent commit activity is absent, and the repository has no security scanning or policy.

Latest 1.1.6

Packagist

62%

Total Score

Maintainer Stability

Dependencies

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has 13 releases but none in the last 12 months, and its latest release was about 8 years ago. This is the strongest evidence of stale maintenance, despite the earlier release history.

Dependency profile

The package declares 24 runtime dependencies, including substantial frontend and framework components. This breadth increases maintenance exposure, although the signal does not show those dependencies are currently unsafe or stale.

Project backing

The repository is owned by an individual rather than an organization, so the single registry maintainer does not benefit from visible organizational backing. This modestly increases continuity risk.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months. This conflicts somewhat with the recent push timestamp but still indicates no demonstrated ongoing development in the measured window.

Repo tooling

Composer is used for builds, providing basic reproducibility support, but no security scanning tool is configured. The missing scanning is a modest transparency and maintenance gap rather than proof of a defect.