jmj/jushuitan-sdk

The package is small and clearly scoped, with straightforward Composer dependencies and no install-time scripts. Its README explicitly warns it has not been used in production, so validation burden remains high.

Latest 0.0.2

Packagist

40%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

Only two releases exist, and the latest was published in January 2022 with no releases in the last 12 months. This is strong evidence of abandonment risk for a package intended as an integration library.

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 recent maintenance capacity.

Package scaffolding

A README is present and this exact version has a GitHub release, which improves transparency. However, the README states the SDK has not been used in production and is for reference, so real-world validation remains weak; the absent package tests and changelog are normal for published artifacts.

Repo tooling

Composer is used for the build, but no security-scanning tooling is present. That leaves dependency and release checks less visible, adding a modest hygiene concern.

Security policy

The repository has no security policy. This is a modest transparency gap for a package handling ERP API credentials, though it is not evidence of a security defect by itself.