jlaso/gps

Release historydanger

This package has had only one release, published in December 2018, with no releases in the last seven years. That is strong evidence of stagnation for a dependency consumers may need maintained over time.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since 2018. The repository is not archived, but there is no observed maintenance to offset the age.

Project backingcaution

The package is backed by an individual repository owner rather than an organization. That is not inherently unhealthy, but it provides less visible maintenance capacity when combined with the single release and inactive commit history.

Repo popularitycaution

The repository has only 2 stars and 2 forks, so there is little visible community activity to provide backup maintenance. Popularity is supporting evidence rather than the main concern, which is the absence of releases and commits.

Security policycaution

The repository has no security policy or security scanning tooling. For this small package this is a secondary transparency gap, but it leaves no documented process for reporting or handling vulnerabilities.