Google Rules and client for SERPS
38%
Total Score
unhealthy
Risky: no release or commit activity since February 2020, plus a repository that does not clearly identify this package.
The latest release was published in February 2020, with no releases in the last 12 months despite the package being over six years old. This is strong evidence of abandonment risk, although the package is not registry-deprecated.
The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observed maintenance capacity.
The linked repository name does not match the package name and its README does not mention the package, leaving the source-to-package relationship unclear. That weakens publication transparency.
The repository has only 1 star, 0 forks, and 0 watchers, providing little evidence of an active user or contributor community. Popularity is supporting evidence rather than decisive on its own, but it does not offset the inactivity.
The linked repository has no security policy, which leaves vulnerability reporting and response expectations undocumented. This adds a maintenance and transparency gap for a package that parses external service results.
We didn't find any vulnerabilities for this package.
| Dependency | Last Release | Score |
|---|---|---|
repat/serps-core Version ^0.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.