Package Health/se7enxweb/explayouts-content-browser

se7enxweb/explayouts-content-browser

This is a young but currently usable and transparently packaged release. It has a stable v1.0.1 version, an explicit GPL-2.0-or-later license with a license file, a matching repository with a substantial README and supporting documentation, no deprecation, no install lifecycle scripts, and a recent repository push. The main concerns are limited maturity evidence—only two releases over 38 days—four commits in the last three months from a single contributor, no tests or changelog in either the artifact or repository, low repository adoption, and no security-scanning tooling. Overall, it appears suitable with normal dependency review, but its maintenance resilience and long-term stability are not yet well established.

Latest v1.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account has publish access. Because the repository owner is a User rather than an organization, this represents a real publishing continuity concern.

Package scaffolding

A substantial README is present and GitHub Releases are used, but neither the artifact nor repository contains tests or a changelog. For a young backend extension this is a genuine, though not severe, maturity gap.

Project backing

The repository is owned by the individual user se7enxweb, not an organization. That aligns with the single-contributor and single-publisher concerns and offers no visible handoff capacity.

Release history

The package is only 38 days old and has two releases, with a 38-day median interval. This shows some release activity but provides limited evidence of mature maintenance.

Repo bus factor

All four recent commits came from one contributor, producing a 100% top-contributor share. With user-owned rather than organization-owned backing, this creates a meaningful continuity risk.