Package Health/n7e/configuration-json-provider

n7e/configuration-json-provider

The package is small and tested, with a clear MIT license and no install-time scripts. Maintenance evidence is thin, with no commits in about nine months and no security policy or scanning. Its source repository also does not clearly mention the package, so verify ownership before adopting it.

Latest 0.3.0

Packagist

62%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Repo commit activity

The repository recorded zero commits and zero active maintainers over the last three months, consistent with the last push being about nine months ago and increasing abandonment risk.

Release history

There are only three releases, all clustered between December 16 and December 17, 2025, with no later release observed over roughly nine months; this gives limited evidence of sustained maintenance.

Repo package mention

The repository name does not match the package name, and no README package mention was available. Although subpackages can use different repository names, the missing corroboration makes the package-to-repository link less clear.

Repo tooling

Composer build tooling is present, but no security-scanning tool was detected. That is a modest repository hygiene gap rather than evidence that the package is unsafe.

Security policy

The repository has no security policy, leaving vulnerability-reporting expectations undocumented. This lowers transparency but is not severe enough to make the release unfit on its own.