jayin/ipgeo

Release historydanger

Only two releases were published, both in June 2022, and there have been no releases in over four years. This is strong evidence of abandonment risk for a package developers may need to maintain over time.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers during the last three months, consistent with the release history showing no activity since June 2022.

Maintainerscaution

One registry account publishes the package. The linked repository is user-owned rather than organization-owned, so there is little visible publishing redundancy or maintainer depth.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tool was detected. That weakens ongoing assurance, especially alongside the absence of recent maintenance.

Security policycaution

The repository has no security policy. This is a transparency and reporting gap, although the package's small scope limits the practical impact.