betagt/localidade

The package includes tests, a stable release, and a small runtime dependency surface. Its single-person ownership, missing security policy, and lack of security scanning leave limited maintenance and oversight capacity.

Latest 1.3

Packagist

38%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in November 2017, with no releases in the following 12 months of observed history; by collection time, this is about 8 years and 10 months without a release. That is strong evidence of abandonment despite three historical releases.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the last push being about 8 years and 8 months earlier. This substantially weakens confidence that defects or compatibility issues will be addressed.

Maintainers

Only one registry account has publish access, creating a thin publishing base. The repository is user-owned rather than organization-owned, so there is no provided organizational backing to compensate for that concentration.

Repo tooling

Composer build tooling is present, but no security-scanning tools were detected. That is a modest supply-chain hygiene gap, especially for a project with no recent maintenance activity.

Security policy

The repository has no security policy. This is a transparency and response-process gap, and the long period of inactivity provides no compensating evidence of active security maintenance.