next/config

Clear licensing, tests, and a minimal dependency footprint support straightforward adoption. Organizational repository backing and a matching source project offset the single registry maintainer, while missing security documentation leaves a modest transparency gap.

Latest 0.2.0

Packagist

65%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Maintainers

Only one account has registry publishing access, which creates some continuity risk; the organization-owned repository provides partial compensation for that thin registry base.

Release history

The package is about 2.9 years old but has only 3 releases, with a median interval of about 12 months and just 1 release in the last 12 months; this indicates slow maintenance.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, which is a concrete sign of currently limited maintenance activity.

Security policy

The linked repository has no security policy, reducing transparency about vulnerability reporting and response expectations.

Version stability

Version 0.2.0 is not a stable major release, although it is not marked as a prerelease and recent releases contain no prerelease versions. This limits maturity confidence without making the package unfit.