yooper/stop-words

Maintainerscaution

Only one registry account has publish access, leaving little publishing redundancy. The package is small and the repository is owned by the same individual, which partly explains but does not remove the continuity risk.

Release historycaution

The package has only two releases and none in nearly nine years, with the latest published in October 2017. That strongly limits evidence of active maintenance, although a static stop-word dataset may need few changes.

Repo commit activitycaution

The repository recorded zero commits and zero active maintainers in the last three months, consistent with no activity since October 2017. This is the clearest evidence of abandonment risk, though the package's static data reduces the impact of inactivity.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small static package this is a modest transparency and maintenance concern rather than a severe dependency risk.

Security policycaution

The repository has no security policy. That weakens the project's process transparency, although the package contains a small data collection and a simple PHP factory.