lawmil/rongcloud

The package is clearly documented, licensed, and lightweight, with tests and examples included. Its maintenance record is the main concern, and the repository has no security policy or scanning tools to add transparency. Pinning this version should be treated as a long-term maintenance risk.

Latest 1.0.2

Packagist

42%

Total Score

Maintainer Stability

Dependencies

100

Maturity

Supply Chain

Health Score Breakdown

Release history

The package has had only 3 releases, all concentrated between April 18 and April 22, 2019, with no releases in the last 12 months. This is strong evidence of abandonment risk for a library dependency.

Repo issue activity

There were no new or closed issues or pull requests in the last month. Combined with the old repository activity, this supports the conclusion that maintenance is inactive.

Repo tooling

Composer is used for builds, but no security scanning tools are configured. That weakens project hygiene evidence without establishing a direct defect in the release.

Repository archived

The repository is not archived, which avoids an explicit abandonment marker, but its last push was on April 22, 2019 and does not offset the long release silence.

Security policy

The repository has no security policy, leaving no documented process for reporting or handling vulnerabilities. This is a transparency gap, though it is less significant than the inactive maintenance record.