at_server/result

Release historydanger

The latest release was published in December 2018, with no releases in the last 12 months. More than seven years without a release is a substantial abandonment concern, despite the package having two stable releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the package's long release gap. This materially reduces confidence that defects or compatibility issues will be addressed.

Package scaffoldingcaution

The artifact includes a README, but it is only 18 characters long and provides very little integration guidance. The absence of tests and a changelog is normal for a published artifact and is not treated as a gap.

Repo toolingcaution

Composer is used for builds, but no security-scanning tooling is present. This is a modest hygiene gap rather than evidence that the release is unsafe.

Security policycaution

The repository has no security policy. This is a transparency and maintenance gap, although the package's very small scope limits how much weight it carries.