joaopaulo/digitalcep

The MIT license and absence of install-time scripts reduce adoption friction. The project has no security policy or scanning, and its single release has seen no repository activity for nearly six years.

Latest 1.0.0

Packagist

45%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, published nearly six years ago, with no releases in the last 12 months. This is strong evidence of an unmaintained package unless the project is intentionally frozen.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old last-push date, this indicates sustained inactivity.

Repo package mention

The repository name does not exactly match the package name, and the README could not be checked for a package mention. This creates some uncertainty about repository ownership, though a naming mismatch can be normal for subpackages.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but these counters provide little supporting evidence of active use or community oversight.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. This is a modest transparency and maintenance gap for a package distributed to consumers.