asgard/captcha

Release historydanger

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

Repo commit activitydanger

The repository recorded no commits and no active maintainers in the last three months, and its last push was over 10 years ago. The organization-owned repository and included tests do not compensate for the lack of recent maintenance.

Package scaffoldingcaution

The artifact includes tests and this version has a GitHub release, both useful transparency signals. However, the published package has no README, which makes integration harder for a library when no published description is available.

Repo toolingcaution

Composer is used as the build tool, but no security scanning tool is configured. The missing scanning is a security-process gap, though it is less severe than the package's long-term inactivity.

Security policycaution

The repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This adds a transparency gap for a package that has seen no recent maintenance.