rindow/rindow-security-core

Release historydanger

Only two releases were published, and the latest was about six years ago; there have been no releases in the last 12 months. This is strong evidence of abandonment risk.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with its last push being about six years ago. No provided signal shows renewed maintenance.

Repo popularitycaution

The repository has zero stars and forks and one watcher, providing little evidence of an active user or maintainer community. Popularity is supporting evidence, so this reinforces but does not determine the result.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. That is a hygiene gap for a security-focused package, although it does not alone establish that the code is unsafe.

Security policycaution

The repository has no security policy. For a library focused on authentication and authorization, this is a meaningful transparency and vulnerability-reporting gap.