troiastudio/tinify
Recent repository activity is limited to one contributor and one commit in three months, with no security policy. Clear licensing, tests, documentation, and organization backing provide useful support but do not offset the stale release history.
48%
Total Score
67
80
75
Health Score Breakdown
The latest registry release was over eight years ago, and there were no releases in the last 12 months. This is strong evidence of a stale published release despite the repository's recent push.
All recent commits came from one contributor. Organization ownership provides some ability to hand maintenance off, but no second active contributor is shown.
The repository recorded only one commit in the last three months from one active maintainer, indicating limited recent maintenance capacity.
The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This is a maintenance and transparency gap, though not severe on its own.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Jan Galek |
Direct Dependencies
| Dependency | Last Release | Score |
|---|---|---|
 nette/di Version ^2.4 | — | — |
guzzlehttp/guzzle Version ^6.3 | — | — |
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 8 years ago
Are You Affected?
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 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.