at_server/verify

Release historydanger

The latest release was published in December 2018, and there have been no releases in nearly eight years. This is strong evidence of abandonment for a package expected to receive maintenance.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap. No provided activity signal compensates for this lack of recent maintenance.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are configured. This is a meaningful maintenance and transparency gap, though it is less serious than the lack of recent development.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This adds a modest transparency concern for a dependency.