The MIT license, matching repository, and simple Composer setup are clear. Documentation includes installation but leaves the description and usage examples unfinished; no security scanning is reported.
35%
Total Score
100
100
56
83
Only two releases were published, with the latest on March 8, 2014 and none in the last 12 months. This long period without releases is strong evidence of abandonment risk.
A README is present and provides installation guidance, but it explicitly leaves the description and usage examples unfinished. Missing tests and changelog files are normal for published package artifacts and are not treated as gaps.
The repository has zero stars, one fork, and one watcher. Low adoption is supporting evidence of limited maturity, but popularity alone does not determine whether a small package is healthy.
Composer is used for builds, but no security scanning tools are reported. This is a transparency and maintenance-hygiene gap, not evidence of unsafe behavior.
The repository is not marked archived, but it was last pushed on February 3, 2014, so the non-archived status does not offset the observed lack of recent maintenance.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
gourmet/common Version * | — | — |
composer/installers Version * | — | — |
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.