raypower/taobao-api

The matching source tree is substantial, the README is present, and the package has only one runtime dependency. Its stable version and lack of install scripts reduce adoption friction, but maintenance and licensing remain unresolved.

Latest 1.0

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

License

No declared license, license file, or repository license file was detected. That creates a material legal and adoption concern for an open-source dependency.

Release history

The package has only one release, published in May 2015, with no releases in the last 12 months. This is strong evidence of abandonment risk for a dependency.

Repo commit activity

There were no commits and no active maintainers in the last three months. Combined with the repository's last push in 2015, this indicates sustained inactivity.

Project backing

The repository is owned by an individual user rather than an organization, so the single registry maintainer does not benefit from visible organizational backing.

Repo tooling

Composer is used as a build tool, which fits the package ecosystem, but no security scanning tooling was detected. This is a modest transparency and maintenance gap.