The repository is clearly tied to the package and includes useful documentation and release notes. MIT licensing and no install-time scripts reduce adoption friction, but they do not offset the long maintenance gap.
32%
Total Score
25
100
75
83
The package has had no release in nearly 11 years and no releases in the last 12 months, despite a short burst of four releases in 2015. This is strong evidence of abandonment risk.
The repository recorded no commits and no active maintainers in the last 3 months, consistent with the nearly 11-year release gap. This materially lowers confidence in ongoing maintenance.
The repository is owned by an individual rather than an organization, so there is no visible organizational backing to offset the single-maintainer context and prolonged inactivity.
Composer is used for the build, but no security-scanning tooling is present. The missing scanning is a hygiene gap rather than evidence of abandonment by itself.
The repository is not archived, which avoids an explicit abandonment marker, but its last push was nearly 11 years ago. The inactivity is already captured more directly by release and commit history.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
cupoftea/package Version ^1.2 | — | — |
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant
ISO 42001Compliant© All Intel data is openly available and commercially licensed.