wucdbm/wucdbm-bundle

There is no security policy or automated security scanning, and the repository has almost no community activity. A clear license, small dependency set, and no install scripts reduce operational friction but do not offset the maintenance concern.

Latest v3.1.7

Packagist

35%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest release was published in March 2017, with no releases in the last 12 months despite the package being nearly 11 years old. This is strong evidence that maintenance has stopped.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the long gap since the last release. This materially raises abandonment risk.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is not decisive, but this provides little supporting evidence of active community oversight.

Repo tooling

Composer is used for the build, but no security scanning tools are configured. The missing scanning reduces ongoing visibility into dependency or repository risks.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. For an inactive project, this is a meaningful transparency gap.