guijianshi/baidu-ocr

Release historydanger

This package has only one release, published nearly eight years ago, with no releases in the last 12 months. That is strong evidence of abandonment risk for a dependency.

Maintainerscaution

A single individual has registry publishing access, leaving little visible maintainer redundancy. The repository is also user-owned rather than organization-backed, so this is a meaningful continuity concern.

Repo toolingcaution

Composer is used for the build, but no security-scanning tooling is present. That weakens assurance about ongoing dependency and code hygiene.

Repository archivedcaution

The repository is not archived, which preserves a path for future maintenance, but its last push was nearly eight years ago and does not counter the release inactivity.

Security policycaution

The repository has no security policy. This is a transparency and response-process gap, though it is less serious than the long period without releases.