andrey-mashukov/throttler
Tests, a release note, and a minimal dependency surface provide some useful structure. The repository has no security policy or scanning, and its single-user ownership offers little visible maintenance capacity.
38%
Total Score
50
100
75
75
Health Score Breakdown
Only two releases exist, with the latest published nearly nine years ago and no releases in the last 12 months. This is strong evidence of abandonment risk for a package that may need fixes or compatibility updates.
The repository is owned by an individual user rather than an organization, so there is no visible organizational backing to compensate for the limited release history.
The repository has zero stars, forks, and watchers. Popularity is not required for a healthy package, but these numbers provide no supporting evidence of community adoption or oversight.
Composer and Phing provide build tooling, but no security scanning tools were detected. This is a transparency and maintenance gap, though it is less severe than the release inactivity.
The repository has no security policy, leaving no visible process for reporting or handling vulnerabilities.
Vulnerabilities
We didn't find any vulnerabilities for this package.
Package versions
Maintainers
 Andrey Mashukov |
Direct Dependencies
No direct dependencies.
Weekly Downloads
Info
- Last Published
- 8 years ago
- Created
- 9 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.