minecraftjp/minecraftjp-php-sdk

Release historydanger

The package has only four releases, all concentrated in 2015, with no releases in the last 12 months and the latest release dating back more than 11 years. 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 no meaningful development for more than a decade. This materially raises abandonment risk.

Repo toolingcaution

The repository uses Composer, showing basic build tooling, but has no security scanning tools. The missing scanning is a modest hygiene gap rather than a standalone adoption blocker.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. For an SDK handling authentication tokens, this is a real transparency gap.