bit3/remote-objects

Registry deprecationdanger

Packagist marks the entire package as abandoned, with no replacement package provided. This is a direct warning against taking a new dependency on it.

Release historydanger

The package has had no releases in more than 13 years: its latest release was in July 2013, despite having four releases overall.

Repo commit activitydanger

There were zero commits and zero active maintainers in the last 3 months, consistent with long-term abandonment rather than active maintenance.

Repository archiveddanger

The linked repository is archived and was last pushed in October 2013, indicating the source project is no longer maintained.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so package-to-source ownership is less clear. The organization-backed repository partly reduces that concern, but does not remove it.