cupoftea/support

Release historydanger

The package has made only two releases, with the latest published over 10 years ago and none in the last 12 months. This is strong evidence of abandonment risk despite the stable version line.

Repo commit activitydanger

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

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. The missing scanning is a modest hygiene concern, not evidence that the release is unsafe.

Security policycaution

The linked repository has no security policy, leaving reporting and response expectations undocumented. This is a meaningful transparency gap for a package with runtime dependencies.