sharapeco/kana-order

Release historydanger

Only two releases exist, with no release in more than four years and a median interval of about four years. This is the clearest maintenance concern, although the repository was not archived.

Repo commit activitycaution

There were no commits from active maintainers in the last three months. This weakens evidence of ongoing maintenance, even though the repository has a recent push timestamp.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That makes the package-to-source relationship less clear and warrants caution.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were detected. For a small library this is a modest transparency and hygiene gap.

Security policycaution

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities.