brightnucleus/contracts

Usable with caveats: the package is small, clearly licensed, correctly backed by an organization, and has no deprecation or dangerous workflow findings. However, it has had no release or repository activity for about 21 months, with only three releases overall, so ongoing maintenance should not be assumed.

Latest v0.2.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only three releases since 2016 and no releases in the last 12 months; the latest release was about 21 months ago. That sparse cadence is a meaningful maintenance concern, although the component is small and may change infrequently.

Repo commit activity

There were no commits and no active maintainers in the last three months, consistent with the long release gap. For a tiny stable interface package this may reflect low change needs, but it still leaves current maintenance capacity un demonstrated.

Repo popularity

The repository has zero stars and forks and only one watcher, offering little supporting evidence of community review or adoption. Popularity is only supporting evidence, so this does not make the package unsafe by itself.

Repo tooling

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a transparency and assurance gap, partly offset by the simple package structure.

Security policy

The repository has no security policy. For a small interfaces package this is not severe, but it leaves vulnerability-reporting and response expectations undocumented.