qixinyun/pingxiang-share-config

Repo commit activitydanger

There were no commits and no active maintainers in the last three months, consistent with roughly four years since the last push. This materially increases abandonment risk.

Release historycaution

Only two releases exist, with no release in about four years and a median interval of roughly three years. This is a meaningful maintenance and abandonment concern for a dependency.

Repo toolingcaution

Composer build tooling is present, but no security scanning tool was detected. The missing scanning is a modest transparency and hygiene gap rather than a severe dependency risk.

Security policycaution

The repository has no security policy. For a small configuration package this is a limited gap, but it reduces clarity about vulnerability reporting and maintenance expectations.

Version stabilitycaution

The assessed version is not a prerelease, which helps, but the package remains on the 0.x line and has limited release history, so maturity is still modest.