struggle-for-php/sfp-iterator-url

Release historydanger

The latest release was in February 2017, with no releases in the last 12 months and only two releases overall. This is strong evidence of abandonment risk, although the package is not marked deprecated.

Repo commit activitydanger

There were no commits or active maintainers in the last three months, consistent with the long release gap and indicating little current maintenance capacity.

Repo package mentioncaution

The repository name does not match the package name and its README does not mention the package, so the repository may not clearly belong to this release. That weakens source transparency.

Repo toolingcaution

Composer build tooling is present, but no security-scanning tooling was detected. This is a modest transparency and hygiene gap rather than evidence of unsafe behavior.

Security policycaution

The repository has no security policy, leaving vulnerability-reporting and response expectations undocumented. This matters for a dependency but does not by itself indicate abandonment.