Package Health/history/campaign-history-report

history/campaign-history-report

The MIT license, minimal runtime dependencies, and lack of install scripts reduce adoption friction. The project has little visible activity or security process, so ongoing maintenance is uncertain.

Latest 2.2

Packagist

46%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The latest registry release was published in May 2024, with no releases in the last 12 months despite a package history spanning about six years. This is a meaningful abandonment concern.

Repo commit activity

The repository recorded no commits and no active maintainers in the last three months, consistent with the long gap since the latest release. This materially lowers confidence in ongoing maintenance.

Repo package mention

The repository name does not match the package name, and no README package mention was observed. Although this can occur with subpackages, the available evidence does not clearly establish that this repository is the package's intended home.

Repo popularity

The repository has zero stars and forks and only five watchers, providing little evidence of an active user or contributor community. Popularity is supporting evidence, but this reinforces the maintenance concern.

Security policy

The linked repository has no security policy, leaving vulnerability-reporting expectations and handling practices undocumented. This is a transparency and maintenance gap.