zen/view

The package is small, licensed, has tests, and uses only one runtime dependency. Its maintenance and transparency are weak: it has had no release or commit activity for nearly 12 years, lacks a README and security policy, and has no security scanning.

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 nearly 12 years ago, with no releases in the last 12 months. That strongly suggests abandonment risk despite the absence of a deprecation notice.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with a project that has been inactive for nearly 12 years. This is strong evidence of limited ongoing maintenance.

Package scaffolding

The artifact and repository contain tests, which supports basic project quality. The missing README is a real consumer-documentation gap for a view library, while the absent changelog is not concerning because changelogs belong in the source project and are not required in published artifacts.

Repo popularity

The repository has zero stars and forks and only one watcher, providing little evidence of community adoption or external oversight. Popularity is supporting evidence rather than decisive on its own, so this remains a caution.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are configured. The missing scanning is a modest transparency and maintenance weakness.