The MIT license, readable documentation, tests, and no install-time scripts reduce adoption friction. The project has had only two releases and no commits in the last three months, while its single-person backing and lack of security tooling increase maintenance risk.
58%
Total Score
50
100
83
75
One registry maintainer is consistent with an individually owned project, but it leaves little visible publishing capacity when paired with the lack of recent repository activity.
Only two releases exist, with the latest published about two years ago and none in the last 12 months. This suggests limited ongoing maintenance, though the package is not deprecated.
The repository recorded zero commits and zero active maintainers in the last three months. Combined with the old latest release, this points to a meaningful abandonment risk.
Composer build tooling is present, but no security scanning tools were found. This is a moderate transparency and maintenance gap rather than evidence that the package is unsafe.
The repository has no security policy, leaving no documented channel or process for handling vulnerabilities. The package's tests and clear source repository provide some compensating transparency, but not a replacement for a reporting process.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
symfony/panther Version ^2.1 | — | — |
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.