francodacosta/caparica

Tests, documentation, and a small runtime dependency footprint make the package straightforward to inspect and integrate. The repository lacks a security policy and automated security scanning, leaving maintenance and vulnerability response less transparent.

Latest 1.0

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in October 2014, and there were no releases in the last 12 months. This long release gap is strong evidence of abandonment risk despite the package having nine historical releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. This confirms that the long release gap is not merely a registry publishing delay.

Repo popularity

The repository has three stars, one fork, and one watcher, indicating limited adoption and a small visible support community. Popularity is only supporting evidence, but it provides little compensating maintenance capacity.

Repo tooling

Composer is used for builds, which fits the package ecosystem. No security scanning tools were detected, reducing automated coverage for a library that handles signed requests.

Security policy

The repository has no security policy, so there is no documented path for reporting vulnerabilities or describing response expectations. This is a transparency and maintenance gap, though not an abandonment verdict by itself.