cachethq/twitter

The repository is public, matches the package, includes tests, and has clear MIT licensing. Releases stopped nearly seven years ago, while repository activity stopped about three years ago; the lack of security scanning adds a smaller maintenance concern.

Latest v3.0.0

Packagist

52%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only three releases were published, all around November 2019, with no release in nearly seven years. That makes compatibility and ongoing maintenance uncertain despite the repository remaining available.

Repo commit activity

There were zero commits and zero active maintainers in the last three months. Combined with the old latest release, this is meaningful evidence of stalled maintenance.

Repo issue activity

There were no new or closed issues and no merged pull requests in the last month, with one open pull request. This adds limited evidence of low current activity but is weaker than the release and commit history.

Repo tooling

Composer is used as the build tool, but no security-scanning tool is configured. The missing scanner is a modest transparency and maintenance gap, not evidence that the package is unsafe.

Security policy

The repository has no security policy. For a small Laravel parser this is a documentation gap, but it provides little evidence about abandonment compared with the stale release and commit activity.