aimer/auxpi

Its single maintainer and one-star repository leave little visible capacity for support or recovery. The MIT declaration, consumer README, and lack of install scripts are reassuring, but the missing security policy limits transparency.

Latest 0.01

Packagist

42%

Total Score

Maintainer Stability

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only two releases, both on June 17, 2019, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the lack of registry releases since 2019.

Maintainers

Only one registry account has publish access, leaving a thin publishing base. The repository is user-owned rather than organization-backed, so there is no provided evidence of broader operational support.

Repo popularity

The repository has one star, two forks, and no watchers. Popularity is supporting evidence rather than a verdict, but these very small figures provide little evidence of an active user or contributor community.

Security policy

The linked repository has no security policy, which reduces transparency for reporting and handling vulnerabilities. This is a meaningful hygiene gap, though it is less serious than the lack of maintenance activity.