roguitar88/consultacep

Its Apache-2.0 license and matching repository make ownership and reuse clearer, while the tiny dependency surface limits complexity. The README is minimal and the project has no security policy, leaving little guidance for consumers or vulnerability reporting.

Latest 1.0.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has only one release, published in August 2021, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the single release from 2021, this indicates a project that is not actively maintained.

Package scaffolding

The package includes a README, but it is only 13 characters long and there are no tests or changelog. Missing tests and changelog are normal for published artifacts; the extremely limited README weakens consumer transparency.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these counts provide no community signal to compensate for the inactivity.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tools are present. The missing scanning is a modest hygiene gap rather than proof of unsafe code.