alfredoem/ragnarok

Release historydanger

The latest of only three releases was published about 10 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a framework integration package.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the release history and leaving compatibility issues unlikely to be addressed.

Maintainerscaution

The registry lists one maintainer. Because the repository is user-owned, this is not inherently abnormal, but it provides limited visible maintainer resilience if that person stops responding.

Repo toolingcaution

Composer is used as the build tool, but no security-scanning tools are present. That leaves an additional unaddressed maintenance and vulnerability-detection gap.

Security policycaution

The repository has no security policy, reducing transparency about vulnerability reporting and response. This is a meaningful hygiene gap, though not evidence of maliciousness by itself.