chipslays/cracker

Release historydanger

The package has had no release in over five years, despite seven releases concentrated in its first few weeks. This is strong evidence of abandonment risk for a dependency.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last three months, consistent with the release history and indicating that maintenance has effectively stopped.

Dependency profilecaution

Three runtime dependencies, including image processing, OCR, and HTTP components, create a meaningful maintenance surface for an otherwise small package. No provided evidence shows these dependencies are unusually excessive or unmanaged.

Project backingcaution

The package and repository are owned by the same individual account, showing a direct ownership link but no organizational backing to compensate for the inactive maintainer.

Repo popularitycaution

The repository has zero stars, one fork, and one watcher. Low popularity is only supporting evidence, but it provides little indication of a broad user or maintainer community.