tusimo/jushuitan

Release historydanger

The package has only 3 releases, all ending nearly 8 years ago, with no releases in the last 12 months. This is strong evidence of abandonment for a dependency.

Repo commit activitydanger

The repository recorded 0 commits and 0 active maintainers in the last 3 months, consistent with the long release gap and leaving no evidence of current maintenance.

Maintainerscaution

A single registry maintainer provides little visible continuity if that person stops maintaining the package. The repository is also owned by the same individual, so there is no broader organization backing shown here.

Repo toolingcaution

Composer is used for the build, which is appropriate, but no security-scanning tools are present. That weakens maintenance assurance without making the release unfit on its own.

Security policycaution

The repository has no security policy, so there is no documented process for reporting or handling vulnerabilities. This is a transparency gap, though not evidence of a vulnerability itself.