at_server/console

Release historydanger

Only two releases exist, with the latest on November 30, 2018 and none in the last 12 months; this is strong evidence of abandonment for a package developers may depend on.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, reinforcing that development is inactive rather than merely released infrequently.

Repo popularitycaution

The repository has zero stars, forks, and watchers, providing no community-maintenance support for the already inactive release history.

Repo toolingcaution

Composer is used for the build, but no security scanning tools are present. This is a modest supply-chain hygiene gap, not evidence that the package is unsafe by itself.

Security policycaution

The repository has no security policy, leaving vulnerability reporting and response expectations undocumented; this is a maintenance and transparency gap, especially alongside the inactive project.