Package Health/stiks/yii2-composer-bower-skip

stiks/yii2-composer-bower-skip

The tiny artifact has no tests, changelog, or security policy, limiting confidence in ongoing support. Its README documents the intended Composer workaround, and the release is licensed, but those positives do not offset the long inactivity.

Latest 2.0.12

Packagist

38%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases are recorded, with the latest on October 6, 2017 and none in the following nearly nine years. This is strong evidence of abandonment for a package expected to support a dependency ecosystem.

Repo commit activity

The repository has recorded zero commits and zero active maintainers in the last three months, consistent with the release history showing no activity since October 2017.

Package file tree

The package contains only README.md and composer.json, with no implementation files visible. That may be intentional for a Composer integration package, but it leaves little evidence of maintained project substance.

Repo tooling

Composer is used as the build tool, which fits the package ecosystem, but no security scanning tooling is present. This is a modest transparency and maintenance gap rather than evidence of a direct defect.

Security policy

The repository has no security policy, leaving vulnerability reporting and response practices undocumented. This compounds the concern created by the lack of recent maintenance.