pishehgostar/exchange-recaptcha

Release historydanger

Only three releases appeared during a brief period ending about 2 years and 8 months ago, with no releases in the last 12 months. This is meaningful abandonment risk for a dependency that may need compatibility updates.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months. Combined with the old last push and release history, this indicates a currently inactive project.

Package scaffoldingcaution

A README is present and documents installation and supported captcha types. The absence of package tests and a changelog is normal for published artifacts; the repository also reports no tests or changelog, limiting project documentation evidence.

Project backingcaution

The registry namespace and repository owner match, and the repository owner is an individual user rather than an organization. This supports consistent ownership but indicates a relatively thin backing structure.

Repo popularitycaution

The repository has zero stars and forks and one watcher. Popularity is only supporting evidence, but these counts provide little evidence of community review or backup maintenance.