se7enxweb/expsite-api

This is a usable but very young package with several positive transparency and safety indicators: it is not deprecated or archived, has a stable v1.0.1 release, includes a README and license file, uses only one runtime dependency, and has recent repository activity. The main concerns are limited maturity—only 2 releases over 38 days—plus a single active contributor responsible for all 5 recent commits, no tests or changelog in either the artifact or repository, and no security-scanning tooling. The package appears consistently backed by its linked repository, so these gaps warrant caution rather than making the dependency unfit, but maintenance continuity remains dependent on one person.

Latest v1.0.1

Packagist

72%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

100

Health Score Breakdown

Maintainers

Only one registry account, 7x, has publish access. This is a thin publishing base and increases continuity risk, with no organizational backing shown by the provided project-backing signal.

Package scaffolding

A substantial README is present, but neither the artifact nor repository contains tests or a changelog. For a library, the lack of visible tests is a genuine maintenance and regression-risk gap, while the README partly compensates for documentation transparency.

Project backing

The linked repository is owned by the individual user se7enxweb, not an organization. This does not invalidate the package, but it provides no organizational succession or maintenance handoff benefit.

Release history

The package is only 38 days old with 2 releases and a median interval of about 25 days. This is too limited a history to demonstrate mature maintenance, though the releases are recent rather than stale.

Repo bus factor

One contributor holds 100% of the 3-month commit activity. With the repository owner identified as an individual rather than an organization, this is a meaningful bus-factor and abandonment concern.