at_server/log

Release historydanger

The package has only one release, first published in October 2018, and no releases in the last 12 months. This is strong evidence of abandonment risk, though a small stable package may not need frequent 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. No provided signal shows current maintenance capacity.

Package scaffoldingcaution

The artifact includes a README, and the absence of tests or a changelog is normal for a published package artifact. The very short README offers limited consumer documentation.

Project backingcaution

The repository is owned by an individual user rather than an organization, so there is no provided organizational backing to offset the single-maintainer and inactivity concerns.

Repo toolingcaution

The repository uses Composer, but no security scanning tools were detected. The missing scanning coverage is a modest hygiene concern, not evidence of an unsafe release by itself.