kseven/affiliate

Usable with caveats: the package is licensed, clearly packaged, and not deprecated, but it has had only one release and no commits in the last three months. Its tiny repository, lack of security scanning, and absent security policy make long-term maintenance and transparency uncertain.

Latest v1.0

Packagist

58%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

There has been only one release, about two years and two months ago, with no releases in the last year. That leaves limited evidence of sustained maintenance.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing the concern that maintenance has effectively stopped after the initial release.

Repo issue activity

There are no open issues or pull requests and no recent activity. This is not inherently unhealthy for a tiny package, but it also provides no evidence of an active user or maintainer community.

Repo popularity

The repository has zero stars and forks and only one watcher. Popularity is supporting evidence rather than a verdict, but these figures provide no meaningful external validation.

Repo tooling

Composer is used for builds, but the repository has no security scanning tools. For a dependency intended to handle affiliate API access, that is a transparency and maintenance gap.