br0sk/yiiron

Release historydanger

The latest release was December 20, 2014, with no releases in the last 12 months. This long release gap is strong evidence of abandonment risk despite the package having seven historical releases.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the absence of releases since December 2014. This materially lowers confidence in ongoing maintenance.

Project backingcaution

The package and repository are owned by the same individual account, with no organization backing shown. This is consistent ownership but offers limited evidence of maintenance capacity.

Repo toolingcaution

Composer and Phing are used for project builds, showing some build structure. However, no security-scanning tooling is present, which is a minor transparency gap for a dependency that has been inactive for years.

Security policycaution

The repository has no security policy. This is a transparency gap, although the package's small scope and inactive state make it less significant than the long maintenance gap.