qixinyun/hexi-share-config

Release historydanger

Only two releases exist, with none in roughly 4 years and 7 months; the long gap is strong evidence of abandonment risk for a package taken as a dependency.

Repo commit activitydanger

The repository recorded zero commits and zero active maintainers in the last 3 months, consistent with the release gap and indicating no recent maintenance.

Maintainerscaution

One registry maintainer provides a thin support base, increasing continuity risk if that person stops maintaining the package.

Repo toolingcaution

Composer build tooling is present, but no security scanning tools were observed, leaving release and dependency issues with less automated oversight.

Security policycaution

The repository has no security policy, so users have no documented path for reporting vulnerabilities or understanding security response expectations.