Organization backing, repository tests, a clear README, and matching license files support continued use. The workflow leaves both action references unpinned and the repository has no security policy, adding maintenance and build-hygiene concerns.
64%
Total Score
75
100
88
83
The package has 11 releases since January 2019, but none in the last 12 months; its latest release was about 18 months ago. This is a meaningful sign of slowed maintenance, although the repository was pushed more recently.
There were zero commits and zero active maintainers in the last 3 months. Together with no releases in the last year, this indicates a materially slowed maintenance cadence.
Composer build tooling is present, but no security scanning tools were detected. That is a modest transparency and maintenance gap, not evidence that the package is unsafe.
The repository has no security policy. This weakens vulnerability-reporting transparency, though it does not by itself indicate abandonment.
The single workflow was fully analyzed with no dangerous triggers, untrusted checkouts, script injection, or audit findings. However, both of its action references are unpinned, which is a build-hygiene caution.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
willdurand/geocoder Version ^4.0|^5.0 | — | — |
geocoder-php/common-http Version ^4.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.