ham0mer/afdian

The package is small, clearly documented, MIT-licensed, and has no install-time scripts. Its single maintainer and lack of security tooling provide little evidence of ongoing support for a dependency handling authentication and payment data.

Latest v1.2

Packagist

47%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had no release in nearly four years and made no releases in the last 12 months, despite reaching a stable v1.2. The short burst of three releases in October 2022 does not compensate for the prolonged silence.

Repo commit activity

The repository recorded zero commits and zero active maintainers in the last three months, consistent with the long release gap and indicating no observable ongoing maintenance.

Maintainers

Only one registry account has publish access, so continuity depends on a single individual. This is a meaningful resilience concern for a package with no recent activity, though it does not by itself show abandonment.

Repo tooling

Composer build tooling is present, but no security scanning tools are configured. That weakens maintenance transparency for a package that handles authentication credentials and payment-related API data.

Security policy

The linked repository has no security policy, leaving no documented channel or process for reporting vulnerabilities. This is a secondary transparency gap alongside the absence of recent maintenance.