sevenrich/api-captcha

Release historydanger

The latest release was over 7 years ago, with no releases in the last 12 months; the five releases were concentrated around the initial publication period. This is strong evidence of abandonment risk.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with a project that has been inactive for years. No provided signal shows active maintenance to offset this.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package. That makes the repository-to-package relationship unclear rather than ordinary monorepo naming.

Repo popularitycaution

The repository has zero stars and watchers and only one fork. Popularity is supporting evidence rather than a verdict, but these values provide no evidence of a broad active user or contributor base.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tools were detected. For a small package this is a hygiene gap, and it adds little confidence given the long inactivity.