Package Health/effective-solutions/security-bundle

effective-solutions/security-bundle

It has a README, tests, an MIT declaration, and a matching organization-owned repository. Its minimal dependency set and lack of install scripts reduce integration and installation risk, but no security policy or scanning leaves transparency limited.

Latest 0.0.3

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only 3 releases, with none in the last 12 months; its latest release was on February 2, 2017. This long period without releases is strong evidence of abandonment risk.

Repo commit activity

The repository recorded 0 commits and 0 active maintainers in the last 3 months, corroborating the package's extended inactivity and increasing abandonment risk.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. This is a transparency and maintenance-hygiene gap, though it is less severe than the absence of recent development.

Security policy

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For a security bundle, this gap is relevant to ongoing maintenance confidence.

Version stability

Version 0.0.3 remains below a stable 1.0 release, so API maturity is uncertain. The absence of prerelease labeling provides only limited compensation.