Its scope is narrow and the dependency surface is minimal. The package has seen no commits or releases for more than three years, while its small, unstarred repository has no tests or security policy. The MIT license and usable README provide some transparency.
45%
Total Score
0
100
75
75
Only two releases were published, with the latest more than three years ago and none in the last 12 months. That long release gap is a substantial abandonment concern, despite the stable 1.0.6 version.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the prolonged release gap. No provided activity signal compensates for this inactivity.
The repository has zero stars, forks, and watchers, offering no supporting evidence of a broader maintenance or user community. Popularity is only supporting evidence, so this reinforces rather than determines the risk.
Composer is used for builds, but no security-scanning tooling is present. This is a modest hygiene gap and does not outweigh the stronger maintenance concerns.
The repository has no security policy, leaving no stated process for reporting or handling vulnerabilities. This is a transparency gap for a package that handles API credentials and requests.
We didn't find any vulnerabilities for this package.
No direct dependencies.
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.