ossbrownie/esputnik

Release historydanger

The latest release was published about eight years ago, with no releases in the last 12 months; this is strong evidence of an aging and likely unmaintained release line.

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, indicating no current development activity to address defects or compatibility changes.

Project backingcaution

The registry namespace and repository owner match, and the repository is owned by a user account; this supports ownership continuity but does not provide organizational maintenance capacity.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected; this is a modest transparency and maintenance gap rather than evidence that the package is unsafe.

Repository archivedcaution

The repository is not archived, but its last push was about five years ago, which supports the broader concern that maintenance has effectively stopped.