The package has tests, a README, a matching repository, and a stable release. Its last release and repository push were in August 2017, with no recent commits, so maintenance confidence is limited.
56%
Total Score
50
100
83
88
The package and repository are owned by the same individual account, providing a direct ownership match but no organizational backing to offset the single-person maintenance risk.
The package has had no release in about 9 years and none in the last 12 months. Its four-release history shows a mature but inactive project rather than ongoing maintenance.
There were no commits and no active maintainers in the last 3 months, consistent with the last repository push being about 9 years ago. This is the main maintenance concern.
The repository has zero stars, forks, and watchers. Popularity is only supporting evidence, but the absence of any visible adoption adds modest uncertainty alongside the long inactivity.
The project uses Composer and Phing, showing basic build tooling, but no security-scanning tool was detected. That is a hygiene gap rather than a severe dependency risk.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
andrey-mashukov/throttler Version 1.0 | — | — |
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.